github github
star 3,019
alert-circle 89
users 42
git-branch 100




Neorg - An Organized Future

Neovim Discord License Status

Your New Life Organization Tool - All in Lua

SummaryShowcaseInstallationSetupUsage ModulesRoadmapPhilosophyFAQ


Neorg (Neo - new, org - organization) is a Neovim plugin designed to reimagine organization as you know it. Grab some coffee, start writing some notes, let your editor handle the rest.

What is Neorg?

Neorg is an all-encompassing tool based around structured note taking, project and task management, time tracking, slideshows, writing typeset documents and much more. The premise is that all of these features are built on top of a single base file format (.norg), which the user only has to learn once to gain access to all of Neorg's functionality.

Not only does this yield a low barrier for entry for new users it also ensures that all features are integrated with each other and speak the same underlying language. The file format is built to be expressive and easy to parse, which also makes .norg files easily usable anywhere outside of Neorg itself.

To learn more about the philosophy of the project check the philosophy section.

:exclamation: IMPORTANT: Neorg is alpha software. We consider it stable however be prepared for changes and potentially outdated documentation. We are advancing fast and while we are doing our best to keep the documentation up-to-date, this may not always be possible.

🌟 Showcase

First class treesitter support

Treesitter powered editing

Powerpoint-like presentations in Neovim with the presenter module

Plus fancy completion powered by nvim-cmp.

Get syntax highlighting for any language supported by Neovim

🔧 Installation

Neorg requires at least Neovim 0.8+ to operate.

You can install it through your favorite plugin manager:

- Packer

use {
    config = function()
        require('neorg').setup {
            ... -- check out setup part...
    requires = "nvim-lua/plenary.nvim"

Every time Neorg hits a new release, a new tag is created by us, so you don't have to worry about all the updates inbetween. That means that adding tag = "*" in Packer will update to latest stable release.

You can also pin Neorg to one specific version through e.g. tag = "0.0.9".

Want to lazy load? You can use the ft key to load Neorg only upon entering a .norg file:

use {
    -- tag = "*",
    ft = "norg",
    after = "nvim-treesitter", -- You may want to specify Telescope here as well
    config = function()
        require('neorg').setup {

Although it's proven to work for a lot of people, you might need to take some additional steps depending on how your lazyloading system and/or Neovim config is set up.

  • Plug 'nvim-neorg/neorg' | Plug 'nvim-lua/plenary.nvim'

    You can then put this initial configuration in your init.vim file:

    lua << EOF
    require('neorg').setup {


Be sure to have nvim-treesitter installed on your system for this step!

Neorg will automatically attempt to install the parsers for you upon entering a .norg file if you have core.defaults loaded. A command is also exposed to reinstall and/or update these parsers: :Neorg sync-parsers.

It is important to note that installation via this command isn't reproducible. There are a few ways to make it reproducible, but the recommended way is to set up an update flag for your plugin manager of choice. In packer, your configuration may look something like this:

use {
    run = ":Neorg sync-parsers", -- This is the important bit!
    config = function()
        require("neorg").setup {
            -- configuration here

With the above run key set, every time you update Neorg the internal parsers will also be updated to the correct revision.

Troubleshooting Treesitter

  • Not using packer? Make sure that Neorg's setup() gets called after nvim-treesitter's setup.
  • If on MacOS, ensure that the CC environment variable points to a compiler that has C++14 support. You can run Neovim like so: CC=/path/to/newer/compiler nvim -c "TSInstallSync norg" in your shell of choice to install the Neorg parser with a newer compiler. You may also want to export the CC variable in general: export CC=/path/to/newer/compiler.

📦 Setup

You've got the basic stuff out the way now, but wait! That's not all. You've installed Neorg - great! Now you have to configure it. By default, Neorg does nothing, and gives you nothing. You must tell it what you care about!

Default modules

Neorg runs on modules, which are discussed and explained in more depth later on. Each module provides a single bit of functionality - they can then be stacked together to form the entire Neorg environment.

The most common module you'll find is the core.defaults module, which is basically a "load all features" switch. It gives you the full experience out of the box.

The code snippet to enable all default modules is very straightforward:

require('neorg').setup {
    load = {
        ["core.defaults"] = {}

You can see here which modules are automatically required when loading core.defaults.

⚙ Usage

A new and official specification is in the works, we recommend reading it here. You can view a summary directly in your neovim instance by running :h neorg if you don't like reading a lot!

Afterwards it's as simple as hopping into a .norg file and typing away.

A good first step is to require the core.norg.dirman module, it'll help you manage Neorg workspaces. Workspaces are basically isolated directories that you can jump between:

require('neorg').setup {
    load = {
        ["core.defaults"] = {},
        ["core.norg.dirman"] = {
            config = {
                workspaces = {
                    work = "~/notes/work",
                    home = "~/notes/home",

Changing workspaces is easy, just do :Neorg workspace work, where work is the name of your workspace. Voila!

It works, cool! What are the next steps?

We recommend you add some core modules that can greatly improve your experience, such as:

  • Using the concealer module to enable icons (core.norg.concealer)
  • Setting up a completion engine (core.norg.completion)

Setting these up is discussed in the wiki, so be sure to check there!

You're now basically set! The rest of this README will be additional information, so keep reading if you care about what makes Neorg tick, or you want to genuinely get good at using it.

🥡 Modules

As you saw previously, we loaded core.defaults and recommended that you load core.norg.dirman. As you probably know those are modules. But what are they, exactly?

Modules are basically isolated bits of code that provide a specific subset of features. They can be docked into the environment at any time and can be essentially stacked together like lego bricks! They can bind themselves to events and callbacks and communicate with each other.

To require a module, just do:

require('neorg').setup {
    load = {
        -- Require the module with the default configurations for it
        ["your.required.module"] = {},

        -- Require the module, and override the configurations (with the "config" table)
        ["your.required.module"] = {
            config = {
                some_option = true

As always, for a little more info you can consult the wiki page here. To know which configurations are provided by default for a module, just click on their link: you'll go to the module page in the wiki.

Core Modules

Here is a list of core modules that aren't part of core.defaults and can be added individually by you.

Feel free to try by adding them to your Neorg setup.

Module name Description
core.gtd.base Manages your tasks with Neorg using the Getting Things Done methodology.
core.norg.completion A wrapper to interface with several different completion engines.
core.norg.concealer Enhances the basic Neorg experience by using icons instead of text.
core.norg.dirman This module is be responsible for managing directories full of .norg files.
core.norg.journal Easily create files for a journal.
core.norg.qol.toc Generates a Table of Contents from the Neorg file.
core.presenter Neorg module to create gorgeous presentation slides.

External Modules

Users can contribute and create their own modules for Neorg. To use them, just download the plugin with your package manager, for instance with Packer:

use {
    requires = "john-cena/cool-neorg-plugin",

After that it's as easy as loading the module it exposes normally:

require('neorg').setup {
    load = {
        ["cool.module"] = {},
Module name Description
core.integrations.telescope Neorg integration with Telescope
external.gtd-project-tags Provides a view of tasks grouped with a project tag. Requires core.gtd.base
external.integrations.gtd-things Use Things3 database to fetch and update tasks instead. Requires core.gtd.base
external.context Display headings in which you are at the top of the window in a float popup.
external.kanban Display your gtd todos in a kanban-like board in floating windows. Requires core.gtd.base

If you ever end up making a module for Neorg feel free to make a pull request and add it to this README!

❓ Philosophy

Our goals are fairly simple:

  1. Revise the org format: simple, extensible, unambiguous. Will make you feel right at home. Alternate markup formats have several flaws, but the most notable one is the requirement for complex and slow parsers. What if we told you it's possible to alleviate those problems, all whilst keeping that familiar feel? Enter the .norg file format, whose specification can be found here. The cross between all the best things from org and the best things from markdown, revised and merged into one.

  2. Keybinds that make sense: vim's keybind philosophy is unlike any other, and we want to keep that vibe. Keys form a "language", one that you can speak, not one that you need to learn off by heart.

  3. Infinite extensibility: no, that isn't a hyperbole. We mean it. Neorg is built upon an insanely modular and configurable backend - keep what you need, throw away what you don't care about. Use the defaults or change 'em. You are in control of what code runs and what code doesn't run!

  4. Logic: everything has a reason, everything has logical meaning. If there's a feature, it's there because it's necessary, not because two people asked for it. If something has a more niche use case, it should be documented.


The wiki is the go-to place if you need answers to anything Neorg-related. Usage, Keybinds, User Callbacks, Modules, Events? It's all there, so we recommend you seriously go read it!


Have an idea? An improvement to existing functionality? Feedback in general?

We seriously recommend you join our discord to hang out and chat about your ideas, plus that you read the CONTRIBUTING.md file for more info about developer-related stuff!


Massive shoutouts go to all the contributors actively working on the project together to form a fantastic integrated workflow:

  • mrossinek - for basically being my second brain when it comes to developing new features and adding new syntax elements
  • danymat - for creating the excellent GTD workflow in Neorg that we literally use internally to plan new features

And an extra thank you to:

  • Binx - for making that gorgeous logo for free!
  • bandithedoge - for converting the PNG version of the logo into SVG form


Love what I do? Want to see more get done faster? Want to support future projects? Any sort of support is always heartwarming and fuels the urge to keep going :heart:. You can show support here: