What Is FlyText? A 2 MB Native Text Editor for Windows

FlyText is a lightweight text editor for Windows with a ~2 MB main binary, built on pure Win32 + Scintilla. No plugin marketplace, no background processes, no telemetry, and no runtime dependencies — copy it onto a clean Windows 7 machine and it just runs.

The one-line positioning: when you need to open a 2 GB log file, or just tweak two lines of a config without waiting 8 seconds for an IDE to boot, it's the better tool for the job.

Why build a 2 MB editor in 2026

This deserves a straight answer, because it drives every design decision in FlyText.

For the past decade the editor story has been "platform": VS Code traded a WebView shell (Electron) for cross-platform reach and an ecosystem; Sublime traded a Python plugin system for customizability. Both roads work — but the costs are real. VS Code's installer is roughly 350 MB, cold start easily exceeds 5 seconds with dozens of extensions, and idle memory often sits above 500 MB.

Meanwhile, one class of work was never covered by that story:

• An ops engineer needs to open a 3 GB nginx.access.log to hunt down one error;
• An analyst wants a quick look at the first rows of an 800 MB CSV;
• A developer on a low-spec machine at a customer site just needs to edit one .env;
• An engineer on a classified project needs AI autocomplete, but the code can never leave the intranet.

These jobs share three traits: tiny task, huge file, poor environment. Launching an IDE for them is overkill — and that overkill often can't do the job at all.

Technology choices: why Win32 + Scintilla

FlyText is C++ calling the Win32 API directly, uses Scintilla as the editing control, and statically links the C runtime with /MT. That combination buys three things:

Choice	Direct result	Trade-off
Pure Win32	No WPF/.NET/VC runtime dependencies; runs on Windows 7+ with nothing to install	Not cross-platform (macOS / Linux versions in development)
Scintilla editing control	Battle-tested syntax highlighting, folding and markers; dozens of languages out of the box	Less flexible to extend than a web stack
Statically linked CRT	A single, self-contained exe; the portable build is unzip-and-run	Slightly larger binary (still ~2 MB)
No plugin runtime	Fast startup, small crash surface, no third-party code injection	The feature boundary is set by the official build

How "instant open" works for huge files

This is the question FlyText gets asked most. The core is chunked loading: instead of reading the whole file into memory, FlyText scans it once to build a line-offset index, then loads only the text chunks near the viewport into Scintilla, swapping them in on demand as you scroll.

Compare the common approaches:

• Read everything + highlight everything (Notepad and most lightweight editors): a 2 GB file means 2 GB of resident memory plus one O(n) syntax scan — the classic symptom is a long unresponsive window or an outright OOM.
• Memory mapping (mmap): solves the memory footprint, but syntax highlighting still requires lexing the whole buffer, so scrolling into unanalyzed regions stutters.
• Chunked loading + viewport-only highlighting (FlyText): the index pass is one fast O(n) scan with no lexing; after that, highlighting happens only in the visible region and is essentially decoupled from file size.

The honest limits: extremely long single lines (hundreds of MB in one line) still hurt — the same structural limitation as every line-based editor. And full-file regex over 2 GB still takes time — FlyText makes it interruptible with live progress, rather than pretending to freeze.

Local AI autocomplete: optional, and genuinely local

AI autocomplete in FlyText is an optional component. After installing the FlyAI inference service, the editor shows ghost-text suggestions in gray; press Tab to accept.

The fundamental difference from Copilot-style services is the data flow: FlyAI runs inference on your own machine, so your code, context and prompts never leave the device, and it works with the network unplugged. That makes it the only viable autocomplete option for intranet development, classified projects and customer sites where even a cloud connection is impossible.

The costs are equally clear: FlyAI is about 943 MB, needs some local compute, and completion quality depends on the model you pick — usually below a cloud LLM. Without it, every other FlyText feature is unaffected.

Feature list

• Syntax highlighting for dozens of languages, with light/dark adaptive color schemes
• Multi-tab + pinned tabs + session restore; scrollable tab bar with an overflow dropdown
• Outline panel: functions / variables / headings as a structured navigation tree, click to jump
• Find & replace: case sensitivity, whole word, regex, capture groups, live highlighting
• HEX viewing and editing mode
• Split view, bookmarks (F2)
• Column editing (Ctrl + drag), line editing (copy / delete / move / join)
• Code folding, bracket matching, auto-closing brackets and quotes, smart indent
• 20 UI languages, 7 themes, custom shortcuts via keybindings.json
• Crash recovery, autosave on focus loss, auto-reload on external changes
• File hash tool: MD5 / SHA-1 / SHA-256 / SHA3-256 / Keccak-256

Who FlyText is NOT for

Being clear about the boundaries matters more than listing features. FlyText probably isn't your daily driver if:

• You depend on a plugin ecosystem: you need LSP, debuggers, a Git GUI, language-specific tooling — use VS Code or a JetBrains IDE.
• You're on macOS or Linux: currently Windows only; other platforms are in development.
• You need real-time collaborative editing: FlyText is a single-user, offline tool.

On the other hand, if you live inside huge logs, dump files and datasets — or you just want an editor that "opens when you click, closes when you're done" — it's worth a try.

On privacy

FlyText has no telemetry, no ads, no bundles, and no resident background processes. Its only network call is a one-time version check when the settings window opens — it carries no device or file information. The sole exception is FlyAI, which you install voluntarily — and even that runs inference locally only.

FAQ

Is FlyText free?

You can download and use it at no cost. Licensing is one-time ($39 for 1 year of updates / $99 for 5 years), with free updates for the license term. Editing is not restricted in the unactivated version.

How does it compare to Notepad++?

Mainly in three areas: chunked loading for GB-scale files, a complete HEX mode, and optional local AI autocomplete (Notepad++ AI plugins mostly go through the cloud). See our Notepad++ alternatives comparison.

Per-device or per-user licensing?

Per device — one machine, one device code. Volume licenses (50+) get 30–60% off; see "Resellers" in the site navigation.

Will there be macOS / Linux versions?

In development. The current architecture is deeply tied to Win32, so a cross-platform build requires rewriting the window layer — there's no firm date yet.