Pragtical is a free and open source code editor (MIT license) that, in our test, used 7 times less RAM than VS Code without extensions. Its version 3.14.0, released on October 20, 2026, adds application menus, a movable command palette, saveable work sessions, and a redesigned Plugin Manager. If you’re comparing code editors and looking for a lighter alternative to Visual Studio Code (what in English is searched as lightweight code editor or VS Code alternative), here are the facts.
What is Pragtical and how does it differ from Lite XL?
Pragtical is a desktop and cross-platform code editor (Windows, Linux, and macOS) that its own documentation presents as a lightweight alternative to web-based technology editors like VS Code. It was born as a fork of Lite XL, which in turn is a fork of lite, the minimalist editor by rxi. The difference with Lite XL is one of philosophy: its maintainers decided to prioritize practicality over minimalism, so Pragtical comes with more features out of the box and releases versions more frequently.
Three technical decisions explain why it weighs so little:
- Native core with LuaJIT. It’s written in C and Lua, and the official builds use LuaJIT instead of standard Lua.
- SDL instead of a browser. There’s no Electron or Chromium underneath. The download for Mac with Apple Silicon weighs 5.85 MB.
- Everything extends in Lua. Most features are plugins. LSP support, integrated terminal, code formatters, and a version control panel for Git and Fossil are available as plugins.
What’s new in Pragtical 3.14?
The main novelty is that you no longer need to memorize commands. Until now, Pragtical assumed you knew the name of each command or its keyboard shortcut.
- Application menus. Commands now appear in the File, Edit, Search, View, Tools, and Help menus, and plugins can add their own entries. Borderless mode and the menu bar come enabled by default, with the menu integrated next to the logo in the title bar. You can change both in Settings > Core > User Interface.
- Movable command palette. The Command Palette Position option offers Bottom, Top, or Center. With Center, the command box floats over the editor instead of resizing your panels. You can also pin it in your user module:
local config = require "core.config"
config.commandview_position = "center"
- Project search, wherever you prefer. Global search can stay on the left, move to the right, or open as a centered floating window (Settings > Plugins > Project Search > Position).
- Work sessions. In File > Sessions you choose which saved session to load and delete the ones you no longer need. Before switching, Pragtical makes a backup of your current workspace, including unsaved text.
- A new Plugin Manager. It has search, category and status filters, sorting, a details panel, and checkboxes to install, update, or uninstall multiple plugins at once.
- File count in the tree. An included plugin, disabled by default, shows how many files are inside each collapsed folder.
How much RAM and CPU does Pragtical use compared to VS Code?
On memory the difference is clear: Pragtical used about 121 MB versus 849 MB of VS Code without extensions (7 times less) and 1418 MB of VS Code with its usual extensions (more than 11 times less). On CPU with the window unfocused, however, the result is tighter, and VS Code without extensions was the one that consumed the least.
The project claims that version 3.14 lowered CPU usage with the window unfocused from 1.6 to about 0.24 percent of a core, because the main loop now waits for SDL events instead of constantly waking up. This is a measurement from the project itself, and its notes clarify that the result depends on the workload and active plugins. That’s why we measured it ourselves:
| Editor | Configuration | CPU unfocused (of a core) | RAM |
|---|---|---|---|
| VS Code | with its usual extensions | 1.15 % | 1418 MB |
| VS Code | --disable-extensions |
0.05 % | 849 MB |
| Pragtical 3.14.0 | by default | 0.83–0.99 % (3 measurements) | 121–148 MB |
What the data shows:
- RAM is the real advantage. In each simultaneous measurement, Pragtical used between 7 and 11 times less memory than VS Code. The gap doesn’t come from extensions: even with all of them disabled, VS Code needed almost 850 MB.
- CPU is a tie against everyday VS Code (0.98 versus 1.15 percent of a core). Against VS Code without extensions, Pragtical consumed more.
- We didn’t reproduce the project’s 0.24 percent. On our machine, Pragtical moved between 0.83 and 0.99 percent of a core. We don’t yet know what explains the difference: the open project, included plugins, or hardware could play a role.
How we measured it: a Mac with Apple M5 Pro and 24 GB of RAM, macOS 27.0.1. We opened the same medium-sized project in both editors, let them stabilize for two minutes, and with Terminal in the foreground, took a sample every 2 seconds for 60 seconds. We summed all processes from each application, because VS Code functions as several Electron auxiliary processes. Two caveats: the CPU value reported by ps on macOS is a smoothed average, and summing the memory of auxiliary processes counts twice some of the memory they share.
How to install Pragtical on Windows, Linux, and macOS?
Download the build for your system from the version 3.14.0 page:
Windows. Run the installer (Pragtical-v3.14.0-x86_64-setup.exe) or unzip the zip. The installer also includes a portable mode. With Scoop:
scoop bucket add extras
scoop install pragtical
Linux. Use the AppImage (you may need to install fuse) or the portable tar.gz file. Official builds require GLIBC 2.35 or higher (Ubuntu 22.04 onwards). The community maintains packages for Arch Linux (AUR) and Fedora:
git clone https://aur.archlinux.org/pragtical.git
cd pragtical
makepkg -si
dnf copr enable sentry/pragtical
dnf install pragtical-nightly
macOS. Open the .dmg (there are separate builds for Apple Silicon and Intel) and drag Pragtical to Applications.
Why does macOS say Pragtical “is damaged”?
The file is not damaged: Pragtical is not signed, and Gatekeeper blocks it with that warning. The solution documented by the project itself is to remove the quarantine attribute:
xattr -cr /Applications/Pragtical.app
If the warning appears when opening the .dmg, run the same command on the .dmg file in your Downloads folder. And if you want to confirm the download is intact before anything else, compare its hash with what GitHub publishes for that file:
shasum -a 256 ~/Downloads/pragtical-v3.14.0-macos-arm64.dmg
For the Apple Silicon build, the result should be ebf07941a9e65ec7f330fff015166046616f1df99beb6d47254d4064703d3f32.
Is Pragtical a free code editor?
Yes. Pragtical is free software under the MIT license: you can download, use, and modify it at no cost, and its source code is public on GitHub.
Can Pragtical replace VS Code as a text editor for programming?
It depends on how much you rely on the VS Code extension ecosystem. Pragtical covers the basic editing cycle out of the box:
- project-wide search and replace, with multiple threads
- code folding
- diff viewer
- Markdown preview
LSP support, terminal, and version control come as plugins. The VS Code marketplace is much broader, so if your workflow lives in specific extensions, Pragtical fits better as a second editor, fast and light: for quick edits, large files, or machines where you don’t want the editor competing for memory. And as our test shows, that memory is what you save the most.
What about you? What editor do you open when you just want to make a quick edit without waiting for your entire environment to load?
- VS Code or a fork (Cursor, Windsurf…)
- A lightweight editor (Pragtical, Sublime Text, Zed…)
- A terminal editor (Vim, Neovim, Helix…)
- I prefer another option (tell us which one)
Comment below or, if this article reached you by email, reply directly to the email: your reply is published here.