Lapce

A fast, native GUI code editor written in Rust, with built-in LSP support, remote development, and a WASM plugin system.

Screenshot of Lapce

Lapce is an open-source, native GUI code editor built with performance in mind. Written entirely in Rust and using its own GPU-accelerated rendering layer (via floem), it aims to be a fast, modern alternative to editors like VS Code — with a modal editing mode, built-in terminal, and a WebAssembly plugin system.

Features

  • GPU-accelerated rendering — buttery smooth UI even on large files, thanks to a custom Rust-native UI framework
  • Built-in LSP — first-class Language Server Protocol support for completions, diagnostics, go-to-definition, and more out of the box
  • Modal editing — Vim-like modal editing mode built in, no plugin required
  • Remote development — connect to a remote machine over SSH and edit files as if they were local
  • WASM plugin system — extend Lapce with plugins compiled to WebAssembly, written in any supported language
  • Built-in terminal — an integrated terminal panel so you rarely need to leave the editor
  • Tree-sitter parsing — fast, accurate syntax highlighting powered by Tree-sitter grammars

Installation

Pre-built binaries are available on the releases page for Linux, macOS, and Windows.

# Arch Linux (AUR)
paru -S lapce

# macOS
brew install --cask lapce

# Nix
nix profile install nixpkgs#lapce

# Debian / Fedora
# AppImage and .deb packages are available on the
# releases page: https://github.com/lapce/lapce/releases

Or build from source:

git clone https://github.com/lapce/lapce
cd lapce
cargo build --release

Plugin System

Plugins are distributed via the Lapce plugin registry and installed directly from within the editor. They are compiled to WASM, making them sandboxed and cross-platform by design. A growing list of language plugins, themes, and tools is available at plugins.lapce.dev.

Status

Lapce is actively developed and in beta. Some rough edges remain, but it is already a capable daily driver for many users, particularly those who value native performance and a lean resource footprint compared to Electron-based editors.