Library / SDK
pkulchenko/ZeroBraneStudio avatar
pkulchenko/ZeroBraneStudio

ZeroBrane Studio: three install routes, a Windows binary in the root, and an unnamed licence

Lightweight Lua-based IDE for Lua with code completion, syntax highlighting, live coding, remote debugger, and code analyzer; supports Lua 5.1, 5.2, 5.3, 5.4, LuaJIT and other Lua interpreters on Windows, macOS, and Linux

2,775 stars520 forksLuaNOASSERTION

At a glance

What is it?
A Lua IDE written in Lua, with local and remote debugging, live coding and static analysis across Lua 5.1 to 5.4 and LuaJIT. The repository carries a Windows executable, a shell launcher, three separate extension directories, documentation links over plain http, and a licence field the project record leaves unasserted.
Who is it for?
ZeroBrane Studio is unusual among IDEs in being written in the language it edits, which is why its plugins, translations and configuration are all Lua or data files a user can read, and its debug surface spans real engines and real frameworks rather than a single interpreter.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 71 days ago.
What is it written in?
Mainly Lua, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • pkulchenko/ZeroBraneStudio2,775 ★ · +4
Star history
Repository2026-10-042026-11-15
pkulchenko/ZeroBraneStudio2.8k2.8k

4 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Three install routes, and a Windows executable committed to the root

Installation offers a platform package for individual systems, a repository snapshot for each of the releases that works everywhere, or a clone of the repository for the current development version, which also works everywhere. None of the three needs compilation, and the README says so directly, adding that scripts to compile the required libraries for all supported platforms do exist under `build/`. The launcher differs by platform and by install type. On Windows you run `zbstudio` from the installation directory or point a shortcut at `zbstudio.exe`. On Linux you run `zbstudio` for a package install and `./zbstudio.sh` for a snapshot or clone. On macOS you launch the ZeroBrane Studio application for a package install and `./zbstudio.sh` otherwise. The tree explains the split: `zbstudio.exe` and `zbstudio.sh` both sit at the repository root, so a clone ships with launchers already in place.

The snapshot route depends on releases the repository record does not show

The second install option is described as downloading a snapshot of the repository for each of the releases, and it links to the repository's releases page. The project record carries no published GitHub releases at all, and the first option is worded as a package for the latest release. So the documented path for getting a specific historical version points at a page that holds nothing to download, while the development version has to come from the default branch instead. That branch is named `master` rather than `main`, and the last push to it is dated 2026-09-06. For a tool whose selling point is attaching to other people's long running processes, the practical consequence is that pinning a known good build is not something the repository itself supports; the tree carries a `CHANGELOG.md` and a `CONTRIBUTING.md`, but no tags to pin against in the release record.

The launch syntax is one line, and the -cfg example stops mid-word

The general form of the command is short:

code
zbstudio [option] [<project directory>] [<filename>...]

An option, an optional project directory, then files to open. The three documented forms are opening files, setting a project directory and optionally opening files, and overriding the default configuration with `-cfg`, which takes a single string of settings separated by semicolons. The example given is `zbstudio -cfg "editor.fontsize=12; edito`, which ends in the middle of a setting name, so the second key in that example is not readable. Since `-cfg` is the documented escape hatch for changing behaviour without editing files under `cfg/`, the one thing a reader cannot copy is a complete example of the mechanism the README introduces it for.

Three extension directories, and the IDE is itself written in the language it edits

Extensibility is listed as three separate mechanisms with three separate directories. Plugins live in `packages/` and provide additional functionality. Translations of menus and messages live in `cfg/i18n/`. User configuration lives in `cfg/`, holding settings for components, styles, colour themes and other preferences. That layout is a direct consequence of the project being written in Lua: the editor loads Lua code as plugins, and a language speaker can read the configuration and extend the tool without a build step, which is also why the repository needs no compilation to run. The rest of the tree follows the same logic, with `src/` for the IDE's own Lua, `lualibs/` for Lua libraries, `interpreters/` for engine definitions, `api/` and `bin/` for entry points, `build/` for the compile scripts and `t/` and `spec/` for the two test trees.

Highlighting covers 125 formats, debugging covers a much shorter list of runtimes

Syntax highlighting and folding are claimed for more than 125 languages and file formats, which is a file extension problem rather than an interpreter problem. The debugger is narrower and is described separately: an integrated debugger with local and remote debugging for Lua 5.1, 5.2, 5.3, 5.4 and LuaJIT, plus other Lua engines through a general documentation page. Framework support is a third category again, and it is the widest: dedicated pages exist for LÖVE, Moai, Gideros, Corona, Marmalade Quick, Cocos2d-x, OpenResty and Nginx, Torch7, Redis, GSL-shell, Adobe Lightroom, Lapis and Moonscript. Those framework pages are hosted on the author's own notebook domain rather than on the documentation site, so the debugging story is split across two hosts, one for interpreter documentation and one for per framework walkthroughs.

Four C libraries are bundled, compiled for every supported Lua version

The IDE ships with several widely used Lua modules rather than asking users to install them: luasocket, luafilesystem, lpeg and luasec, each compiled for all supported Lua versions. That is the reason the tree carries a `build/` directory at all, since those four are native extensions and have to be built against each interpreter the IDE can host, while the IDE's own code does not. The bundled set also explains part of the feature list. Network calls come from luasocket, filesystem access from luafilesystem, pattern matching performance from lpeg, and TLS from luasec, which is what makes an interactive console and a remote debugger usable against a live process without asking the user to assemble a dependency set first. Nothing in the tree pins those four to a particular upstream version, so the copies in the repository are what a clone gets.

The licence field is unasserted, a LICENSE file is present, and the docs are plain http

Three housekeeping facts are worth stating plainly. The project record leaves the licence unasserted, while a `LICENSE` file sits in the repository root, so the two disagree and only the file itself settles what terms apply; nothing here should be read as a claim about which licence it is. Every documentation link in the README is written as plain http rather than https, on both the documentation site and the author's notebook domain, so a reader following them fetches pages over an unencrypted connection. And the default branch is `master` with the last push dated 2026-09-06, which puts the most recent change to this twenty five year old language tool within the last month while also leaving the release record empty.

Editorial conclusion

ZeroBrane Studio is unusual among IDEs in being written in the language it edits, which is why its plugins, translations and configuration are all Lua or data files a user can read, and its debug surface spans real engines and real frameworks rather than a single interpreter. It suits someone who needs to attach a debugger to a Lua process on a device or a server, and it is a poor fit for someone who wants a modern language server experience on a large Lua codebase, since completion and analysis here are the IDE's own scope aware implementation. Three things are worth checking before you commit to it. The project's licence field is unasserted in the repository record while a LICENSE file sits in the root, so read that file yourself rather than assuming. The documentation is served over plain http. And the install routes are unusual: a platform package, a per release snapshot, or a clone, with a committed Windows executable and a shell script as the launchers on the platforms that have no committed binary.

Frequently asked questions

what is zerobrane studio

A lightweight cross platform IDE for Lua, written in Lua itself, with code completion, syntax highlighting, an integrated local and remote debugger, static analysis, live coding and an interactive console. It runs on Windows, macOS and Linux against Lua 5.1, 5.2, 5.3, 5.4, LuaJIT and other Lua engines.

how to install zerobrane studio on linux

There are three routes: the platform installation package, a repository snapshot for each release, or a clone of the repository for the development version. No compilation is needed for any of them. On Linux you then run zbstudio for a package install, or ./zbstudio.sh when you started from a snapshot or clone.

Which Lua engines and frameworks can ZeroBrane Studio debug?

The debugger targets Lua 5.1, 5.2, 5.3, 5.4 and LuaJIT with local and remote debugging, and the project publishes walkthroughs for LÖVE, Moai, Gideros, Corona, Marmalade Quick, Cocos2d-x, OpenResty and Nginx, Torch7, Redis, GSL-shell, Adobe Lightroom, Lapis and Moonscript.

What libraries ship inside ZeroBrane Studio?

luasocket, luafilesystem, lpeg and luasec, each compiled for all supported Lua versions. Syntax highlighting and folding cover more than 125 languages and file formats, and the project view can auto refresh and hide files and directories.

How do you extend ZeroBrane Studio?

Through three directories. Plugins go in packages/ and add functionality, translations of menus and messages go in cfg/i18n/, and user settings for components, styles and colour themes go in cfg/. There is also a -cfg launch option that overrides configuration from a semicolon separated string.

Official sources

  1. Issues
  2. pkulchenko/ZeroBraneStudio on GitHub
  3. Project website
  4. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/pkulchenko-zerobranestudio.svg)](https://hysenlabs.com/projects/pkulchenko-zerobranestudio)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/pkulchenko-zerobranestudio.svg)](https://hysenlabs.com/projects/pkulchenko-zerobranestudio)

Was this useful?