kate-editor.org

What is Kate?

Kate is a free, open-source text editor built on KDE Frameworks and Qt, available for Linux, Windows and macOS. It targets programmers who want a single editor for reading, writing and navigating code across large projects, while remaining comfortable for plain-text editing and note-taking.

Its defining strengths are breadth and depth: syntax highlighting for over 400 languages, LSP-based autocompletion, multi-cursor and rectangular block selection, VI input mode, scriptable auto-indentation, and bracket-aware navigation. Files open in tabs or split views, and a project sidebar plus project-wide search and replace handle multi-file work. Plugins ship by default, including an embedded terminal, SQL execution, GDB debugging, one-click builds, and previews for Markdown, HTML and SVG.

Where Kate fits best

• Developers working across many languages: highlighting and LSP support reduce context-switching between specialist editors.
• People migrating from proprietary editors: every hotkey is configurable, so existing muscle memory can be preserved.
• Mixed text and code work: on-the-fly spellchecking and previews suit writers who also edit markup.
• Terminal-centric workflows: the embedded terminal and build/debug plugins keep work inside one window.

Trade-offs to weigh

Kate is feature-dense, so first launch can feel busy compared with minimal editors; the payoff comes after configuring hotkeys, plugins and layouts. It is also a general-purpose editor rather than a full IDE, so very large refactors or framework-specific tooling may still call for a dedicated environment. If you prefer a lightweight, terminal-first editor, compare with Vim; for an extensible editor with a large extension marketplace, Visual Studio Code is the closer alternative.

A practical first step: install Kate, open one real project folder via the sidebar, enable the terminal and preview plugins, then remap two or three hotkeys you rely on. If the editor feels natural within an afternoon of actual work, it will likely stick.

How does Kate compare to other text editors like VS Code or Sublime Text?

Kate sits in the same broad category as VS Code and Sublime Text — a fast, extensible editor for code and text — but it targets a different priority: a lightweight, native desktop editor built on KDE Frameworks and Qt, rather than a full development environment or a commercial product. If you want an editor that opens quickly, handles many files at once, and gets out of the way, Kate is aimed at you. If you want a built-in debugger, integrated Git UI, and a vast extension marketplace, VS Code is the more natural fit.

Where Kate stands out

• Editing ergonomics. Multi-cursor and multi-selection editing, rectangular block selection, smart comment/uncomment handling, and scriptable auto-indentation are core features rather than add-ons.
• Syntax coverage. Highlighting for over 400 languages, plus bracket matching that helps you navigate nested code blocks.
• Multiple views. Tabs and split views let you work on several files side by side, with a project sidebar and smart tabs for recent documents.
• Search across a project. Search and replace works across an entire project, not just the open buffer.
• Language intelligence. Autocompletion for many languages via the Language Server Protocol, so you get code-aware suggestions without a separate IDE.
• Hotkey freedom. Every shortcut is configurable, which matters if you are migrating from another editor and don't want to relearn muscle memory.
• Bundled plugins. An embedded terminal for running console commands, SQL query execution, GDB debugging, one-click project builds, and a preview for Markdown, HTML, and SVG.
• Spellchecking. On-the-fly checking is included, which is useful for prose and documentation as well as code.

How the three compare in practice

Choosing between them

Ask what you actually do in the editor. If your day is mostly reading, editing, and navigating large codebases or text files — and you prefer a desktop-native feel over a web-technology shell — Kate's combination of split views, project-wide search, and default plugins covers most of it without setup. If you rely on an integrated debugger, Git tooling, remote development, or a specific extension that only exists elsewhere, that ecosystem is the deciding factor. Sublime Text appeals most to people who want a very fast, spare editor and are comfortable assembling features through packages.

A practical test: take one real project and try a typical hour of work in each. In Kate, check whether the embedded terminal, project-wide search, and LSP completion replace the tools you normally reach for. Note which shortcuts you had to change and how long that took. Whichever editor lets you finish that hour without leaving it is the one worth keeping. Kate is available for Linux, Windows, and macOS, and the project's news and background pages are worth a look if you want to understand its long maintenance history: Kate - Get an Edge in Editing.

Can Kate be used as a full IDE for programming, and what language support does it offer?

Yes, Kate can serve as a full IDE for many programming workflows, but it sits closer to a highly extensible code editor than a batteries-included IDE. Its own feature list points to the pieces developers expect: LSP-based autocompletion for many languages, an embedded terminal, GDB debugging, one-click project builds, SQL execution, scriptable auto-indentation, VI input mode, rectangular block selection, and smart comment/uncomment handling.

Language support

Kate's headline claim is syntax highlighting for over 400 languages. That covers reading and editing in almost any language you are likely to touch, and it also understands bracket structure to help you navigate nested code blocks. For actual coding intelligence, the relevant mechanism is the Language Server Protocol: Kate supports LSP autocompletion "for many languages," which means the depth of support depends on which language servers you install and configure rather than on Kate shipping a bespoke engine per language. On-the-fly spellchecking is included for prose and comments.

What this means in practice

A reasonable reader is a developer who works across, say, Python, Rust and JavaScript, and wants one window for editing, a terminal, and debugging. With Kate they would install the relevant language servers, open the project via the sidebar, use split views and smart tabs to move between files, run searches across the whole project, and use the built-in terminal plus GDB integration instead of switching applications. Someone who mainly edits configuration files, Markdown or HTML gets the preview plugin for MD, HTML and SVG, plus multi-cursor editing for repetitive changes.

Trade-offs to weigh

• Configuration is on you. LSP autocompletion and debugging quality depend on setting up language servers and tools; an IDE that bundles a compiler, test runner and refactoring suite for one language will feel more complete out of the box.
• Hotkeys are flexible. Every binding is configurable, so migrating from a proprietary editor does not force retraining.
• Cross-platform. It is available for Linux, Windows and macOS, which helps if your team is mixed.
• Plugin dependence. The terminal, SQL and GDB features are plugins, so the "full IDE" experience is assembled rather than monolithic.

How to decide

If you want a fast, keyboard-driven editor that can be grown into an IDE and you are comfortable installing language servers, Kate is a strong fit. If you want a single-language toolchain with zero setup, compare against a dedicated IDE for that language. To test the fit, install Kate, add one language server for your main language, open a real project, and try a full cycle: edit, run a command in the embedded terminal, set a breakpoint in GDB, and search across the project. Related tools worth knowing are Visual Studio Code and JetBrains.

How do I install Kate on Windows or macOS?

Kate is available for Windows and macOS, and the project points Windows users to the Microsoft Store as one distribution route. For macOS, the official download options on the site are the practical starting point.

Windows

• Check the Microsoft Store listing for Kate first. The site references the Microsoft Store in its own section on KDE software distribution, and a store install handles updates for you.
• If you prefer a standalone installer, look for the official download link on the Kate site rather than a third-party mirror. You get a normal desktop application either way.

macOS

• Use the official download offered for macOS on the Kate site. macOS builds of KDE applications are typically distributed as a disk image or app bundle, so expect a drag-to-Applications style install.
• Expect a first-launch prompt from macOS Gatekeeper, since the app is not distributed through the Mac App Store. You may need to confirm opening it in System Settings under Privacy & Security.

What to expect once it runs

The same editor core is there on both platforms: tabs and split views for multiple files, syntax highlighting for over 400 languages, multi-cursor editing, on-the-fly spellchecking, and plugins that ship by default, including an embedded terminal, search and replace, and a preview for Markdown, HTML and SVG. Language Server Protocol support provides autocompletion for many languages, and you can rebind every hotkey if you are coming from another editor.

If you want a second opinion or a comparison before installing, Kate - Get an Edge in Editing is the authoritative source for download links and feature details.

A quick decision rule: choose the Microsoft Store on Windows if you want automatic updates and don't mind the store ecosystem; choose a direct download if you need a specific version or portable-style control. On macOS, the direct download is the only official path, so budget a minute for the Gatekeeper prompt on first launch.

What plugins are available in Kate and how do they enhance editing?

Kate ships with a set of plugins enabled by default, and the ones highlighted on its site cover four main jobs: running things without leaving the editor, working with structured data, debugging and building, and previewing output.

Plugins described on the site

• Embedded terminal: runs console commands directly inside Kate, so you can build, test or inspect files without switching to a separate terminal window.
• Search and replace: extends Kate's project-wide search with more powerful patterns and replacement options.
• Preview: renders Markdown, HTML and SVG so you can see the result of a file as you edit it.
• SQL: execute SQL queries from the editor.
• GDB: debug your program through the GNU debugger.
• Build: build projects with a single click.

How they change the editing experience

The practical effect is fewer context switches. A typical workflow: open a project folder in the sidebar, edit a Markdown README in one split and its source file in another, run the build from the embedded terminal, then use the preview to check the rendered output — all in one window. The SQL and GDB plugins serve narrower audiences: people querying a database while writing code, and C/C++ developers who want breakpoints and stepping alongside their source rather than in a separate IDE.

What the plugins do not replace

These are editor-level conveniences, not a full IDE. Language intelligence — autocompletion, diagnostics, go-to-definition — comes from Kate's Language Server Protocol support, which is a core feature rather than a plugin. So if your work depends heavily on refactoring tools, integrated test runners or visual debuggers, compare Kate against a dedicated IDE before committing. Conversely, if you mostly edit text and configuration files and only occasionally need to run a command or preview a document, the default plugin set is likely enough.

A sensible next step

Install Kate and open Settings → Configure Kate → Plugins to see the full list and toggle each one. Start with the terminal, search and replace, and preview enabled; add SQL, GDB or build only when a project actually needs them. If you want to compare alternatives first, Visual Studio Code and Sublime Text take different approaches to extensions, and both are worth a look if plugin breadth matters more to you than a lightweight default setup.

How can I customize Kate's hotkeys and interface to match my workflow?

Kate lets you remap nearly every shortcut and rearrange its interface so it fits how you already work. The main places to look are Settings → Configure Keyboard Shortcuts, Settings → Configure Kate, and the View menu for panels and toolbars.

Remapping hotkeys

Kate's shortcut system is built for people migrating from other editors. You can reassign keys at two levels:

• Application shortcuts — global editor actions like save, search, or opening the terminal.
• Plugin shortcuts — actions added by plugins, such as running a build or starting GDB.

In the shortcut configuration dialog, search for a command by name, click its current binding, and press the new key combination. If a conflict exists, Kate flags it so you can resolve the overlap. Because every hotkey is configurable, you can reproduce the muscle memory from a proprietary editor without retraining.

Shaping the interface

Interface customization centers on the panels and views you keep visible:

• Split views — divide the editing area horizontally or vertically to keep multiple files in sight at once.
• Project sidebar — show or hide the directory tree depending on whether you are navigating a large project or editing loose files.
• Tabs — smart tabs surface recently opened documents; you can adjust tab behavior in the configuration pages.
• Toolbars and menus — toggle which toolbars appear so the chrome matches your screen space.

A practical starting point

A developer working across a multi-file project might: enable the project sidebar, open a vertical split for a header and its source file, bind the integrated terminal to a familiar key, and keep the search-and-replace shortcut identical to their previous editor. A writer or note-taker might instead hide the sidebar, enable on-the-fly spellchecking, and use the Markdown preview plugin alongside the text.

Where to go next

Open Settings → Configure Keyboard Shortcuts, filter by the action you use most, and rebind it first. Then open Settings → Configure Kate and step through the Application, Editor, and Plugin sections, since plugin pages are where terminal, SQL, GDB, and build actions get their own keys and visibility settings.

Kate is available for Linux, Windows, and macOS; see Kate - Get an Edge in Editing for the current feature list and download options.