A Neovim and LazyVim port of John Papa's Winter is Coming VS Code theme.
| Colorscheme | Based on | Background |
|---|---|---|
winteriscoming-blue |
Winter is Coming (Dark Blue) | #011627 navy |
winteriscoming-black |
Winter is Coming (Dark Black) | #282822 charcoal |
winteriscoming-light |
Winter is Coming (Light) | #ffffff |
winteriscoming |
follows vim.o.background |
your style / light_style |
Comments and keywords are italic by default. The original theme also italicizes functions, variables, properties and decorators; see Italics to turn that back on.
Real LazyVim sessions (vtsls and pyright for LSP, treesitter for everything else).
![]() |
![]() |
| Completion and explorer · blue | Picker · black |
![]() |
![]() |
| Diagnostics and hover · light | Dashboard · blue |
Font: the screenshots use JetBrains Mono Nerd Font (
brew install --cask font-jetbrains-mono-nerd-font). See the font guide for other good coding fonts, how to set them up in Ghostty, iTerm2, Kitty, WezTerm, Alacritty, Windows Terminal, VS Code and Neovide, and how to turn ligatures on or off.
Create ~/.config/nvim/lua/plugins/winteriscoming.lua:
return {
{
"bytebeast/winteriscoming.nvim", -- or: dir = "~/code/winteriscoming.nvim"
lazy = false,
priority = 1000,
opts = {},
},
{
"LazyVim/LazyVim",
opts = { colorscheme = "winteriscoming" }, -- or "winteriscoming-black", ...
},
{
"akinsho/bufferline.nvim",
opts = function(_, opts)
-- bufferline builds its file icon colors from these
opts.highlights = function()
return require("winteriscoming.groups.bufferline").highlights()
end
end,
},
}LazyVim's lualine uses theme = "auto", which picks up the bundled lualine
theme by itself. The bufferline gets the VS Code tab look (dark inactive tabs, a
lighter navy active tab with a winter-blue marker) by itself too, but bufferline
draws file icons from its own highlights option, so without the block above
the icons sit on a mismatched background. Integrations are enabled for exactly
the plugins lazy.nvim (or vim.pack) has installed, so there is nothing to
list. Full docs: :h winteriscoming; :checkhealth winteriscoming shows what
is active.
Without LazyVim:
require("winteriscoming").setup({ style = "blue" })
vim.cmd.colorscheme("winteriscoming")Everything goes in opts. This spec spells out the stock values of the options
people change most, so copying it as is changes nothing. Edit from there. The
full list of options and defaults is under Configuration.
return {
{
"bytebeast/winteriscoming.nvim",
lazy = false,
priority = 1000,
opts = {
style = "blue", -- "blue", "black" or "light"
transparent = false, -- true lets the terminal background show through
styles = {
comments = { italic = true },
keywords = { italic = true },
functions = {},
sidebars = "dark", -- neo-tree, trouble, help, ...: "dark", "transparent" or "normal"
floats = "dark", -- "dark", "transparent" or "normal"
},
bright_line_numbers = false, -- true = every line number in winter blue, like VS Code
},
},
{
"LazyVim/LazyVim",
opts = { colorscheme = "winteriscoming" }, -- follows `style` above
},
}Warning
Everything in this example is an override. It changes the stock look: no editor background, different keyword, string and function colors, italic functions and parameters, cream cursor line number. Copy only the lines you want.
opts = {
style = "black", -- override: Dark Black instead of Dark Blue
transparent = true, -- override: let the terminal background show through
styles = {
functions = { italic = true }, -- override: italics on top of comments + keywords
sidebars = "transparent", -- override: neo-tree, trouble, help, ...
floats = "transparent", -- override
},
bright_line_numbers = true, -- override: every line number in winter blue
-- override palette colors and roles, applied before highlights are built
on_colors = function(c)
c.ice = "#38c6ff" -- keywords, operators, jump labels, picker matches
c.syntax.string = "#c3f5c6" -- just strings
c.syntax.func = "frost" -- point a role at another palette color
end,
-- override individual highlight groups, applied last
on_highlights = function(hl, c)
hl.CursorLineNr = { fg = c.cream, bold = true }
hl.WinSeparator = { fg = c.blue }
hl["@variable.parameter"] = { fg = c.cream, italic = true }
hl.SnacksPickerMatch = { fg = c.green, bold = true }
end,
}on_colors changes colors at the source, so everything that uses them
follows (changing ice recolors every keyword). on_highlights is for
one-off tweaks to specific groups. The palette names are listed under
Palette; :Inspect on any character shows which group colors it.
Restart Neovim after changing opts.
These are the defaults; pass only what you want to change.
require("winteriscoming").setup({
style = "blue", -- "blue", "black" or "light"
light_style = "light", -- used when 'background' is light
transparent = false, -- don't set the editor background
terminal_colors = true, -- colors for :terminal
hide_inactive_statusline = false, -- inactive statuslines become a thin line
italics = true, -- false drops every italic, comments and keywords included
bold = true, -- false drops every bold attribute
styles = {
-- any attr-list accepted by nvim_set_hl
comments = { italic = true },
keywords = { italic = true },
functions = {},
variables = {},
properties = {},
attributes = {}, -- decorators, tag attributes
parameters = {},
types = {},
strings = {},
operators = {},
virtual_text = {}, -- diagnostic virtual text
inlay_hints = {},
-- LSP semantic modifiers, stacked on the token's color
mutable = {}, -- e.g. { underline = true } for Rust `mut`
readonly = {}, -- e.g. { italic = true }
statics = {}, -- e.g. { bold = true }
globals = {}, -- e.g. { underdotted = true }
sidebars = "dark", -- "dark", "transparent" or "normal"
floats = "dark", -- "dark", "transparent" or "normal"
},
bright_line_numbers = false, -- true = every line number in winter blue, like VS Code
faithful = false, -- true = exact VS Code colors instead of this port's adjustments
dim_inactive = false, -- darken inactive windows
contrast = "normal", -- "high" lifts every syntax color to WCAG AA, plus comments and line numbers
subtle_comments = false, -- true, a fade from 0 to 1, or { fade = 0.7, docstrings = false }
colorblind = false, -- "red-green" or "blue-yellow"
saturation = 1, -- 0 (greys) to 1 (full color); contrast is kept
accent = "blue", -- titles, badges, selected tab, float borders, normal mode
rainbow = "vivid", -- rainbow delimiters and indent scopes: "vivid", "dimmed" or "mono"
rainbow_variables = false, -- a color per local variable (needs LSP semantic tokens)
diagnostics = {
underline = "undercurl", -- "undercurl", "underline" or false
virtual_text = "tinted", -- "tinted" or "plain"
},
inlay_hints = "tinted", -- "tinted" or "plain"
borderless = false, -- pickers framed by shade instead of border lines
bright_borders = false, -- float borders in the full accent color
lualine_bold = false, -- bold mode section in lualine
on_colors = function(colors) end,
on_highlights = function(highlights, colors) end,
cache = true,
plugins = {
all = nil, -- nil: everything, unless lazy.nvim or vim.pack is in use
auto = true, -- with lazy.nvim or vim.pack, only plugins you have installed
-- telescope = true, -- force an integration on or off
},
})Invalid values are reported once and replaced by their defaults.
These change derived colors only; the palette and its role mapping stay as they are.
contrast = "high"lifts every syntax color below WCAG AA (4.5:1) up to it, and brightens comments, line numbers, inlay hints and muted UI text. A few stock colors sit just under AA (light keywords at 4.3:1,templatemagenta at 4.4:1 on navy), so this is the switch for bright rooms and low vision.colorblindremaps git signs, diffs and diagnostics to colors that stay apart under a simulation of each deficiency (Machado et al. 2009), following GitHub's conventions: added and ok are blue, deleted and errors warm. Syntax colors are untouched.subtle_commentsfades comments by contrast, so the same value looks the same in every style, and never below 1.6:1. A comment color you set inon_colorsis left alone.saturationscales color in OKLab and restores each color's contrast, so0.6is calmer without getting harder to read. Git, diff and diagnostic colors keep at least 70% of theirs so they stay distinguishable.accentis one ofblue,sky,azure,periwinkle,teal,aqua,green,lime,cream,amber,coral,rose,pink,lavenderorpurple; every choice besides the default keeps badge text at 4.5:1.rainbow_variablesgives every local variable and parameter its own color from its name, as in JetBrains IDEs: 12 colors (6 withcolorblind), all at AA on the cursorline.
To match the VS Code theme exactly, with code italicized as well:
opts = {
styles = {
functions = { italic = true },
variables = { italic = true },
properties = { italic = true },
attributes = { italic = true },
},
}Changed text inside a changed line (DiffText) is underlined in winter blue as
well as tinted, so a one-character edit doesn't disappear into the line's
tint. Added text inside a changed line (DiffTextAdd) is tinted and
underlined in green. DiffTextAdd needs Neovim 0.12+ with inline:char in
'diffopt'. That's the 0.12 default, but if your config sets diffopt, add it
back:
vim.opt.diffopt:append("inline:char")Folded lines use a neutral shade darker than the editor, so a fold never looks like a changed line.
With cursorline on, Neovim underlines the whole cursor line in diff windows
(the diff background hides CursorLine's, so it marks the line another way).
It happens with any colorscheme whose CursorLine sets only a background,
kissaten included. To keep only the changed text underlined, highlight just
the line number in diff windows:
vim.api.nvim_create_autocmd({ "VimEnter", "WinEnter", "BufWinEnter", "OptionSet" }, {
callback = function()
for _, win in ipairs(vim.api.nvim_list_wins()) do
vim.wo[win].cursorlineopt = vim.wo[win].diff and "number" or vim.go.cursorlineopt
end
end,
})To drop the underlines, override the two groups:
on_highlights = function(hl, c)
hl.DiffText = { bg = c.diff.text }
hl.DiffTextAdd = { bg = c.diff.text_add }
end,Inside tmux, colored underlines need this in ~/.tmux.conf (tmux 3.2+, then
detach and reattach), or they come out in the text color:
set -as terminal-features ",*:usstyle"A few colors are tuned for a terminal, where the original relied on italics to
tell blues apart. faithful = true restores the exact VS Code values.
| Role | This port | VS Code | Why |
|---|---|---|---|
| functions | #8fa2f8 |
#87aff4 |
was nearly identical to constants |
| variables | #b3c8d9 |
#a4ceee |
greyer, so it separates from keywords |
| constants | #a170c6 |
#82aaff |
VS Code's own constant purple |
| comments | #8a9db3 |
#999999 |
cool grey-blue at the same contrast |
| docstrings | #a3c7ba |
#bcf0c0 (string) |
long docstrings read as prose, not a wall of mint |
| Dark Black selection | #2a4258 |
#103362 |
navy turned muddy on charcoal |
With an LSP that sends semantic tokens (vtsls in LazyVim), declared class fields
are white and accessed properties cream, as in VS Code, and globals such as
console use the library teal.
Highlight groups refer to roles (colors.syntax.keyword) that point at
palette names (ice). Roles are resolved after on_colors, so changing a
palette color recolors everything that uses it:
opts = {
on_colors = function(c)
c.ice = "#38c6ff" -- keywords, operators, jump labels, picker matches
c.syntax.string = "#c3f5c6" -- or change one role only
c.syntax.func = "frost" -- or point a role at another palette name
end,
on_highlights = function(hl, c)
hl.CursorLineNr = { fg = c.cream, bold = true }
hl.LineNr = { fg = c.fg_muted }
end,
}Use the palette elsewhere (statusline components, etc.):
local colors = require("winteriscoming").colors() -- or .colors({ style = "light" })Everything comes from the VS Code theme unless noted. Neovim needs more than an editor theme does (diff backgrounds, search, jump labels, an orange), so the palette is expanded with shades derived from the original:
| Name | Blue / Black | Light | Used for |
|---|---|---|---|
ice |
#00bff9 |
#0784a6 |
keywords, operators, this |
blue |
#219fd5 |
#2f86d2 |
cursor, line numbers, statusline, info |
periwinkle / magenta |
#8fa2f8 |
#b1108e |
functions |
mist |
#b3c8d9 |
#6b6b6b |
variables |
violet |
#a170c6 / #ad80d4 |
— | constants |
lavender |
#d29ffc |
#7c2cbd |
types, classes |
cream |
#f7ecb5 |
#b05f0a |
properties, decorators, current search |
mint |
#bcf0c0 |
#a44185 (plum) |
strings |
green |
#8dec95 |
#07805e |
numbers, booleans |
teal |
#7fdbca |
#2f7d70 |
built-in types, hints |
purple |
#c792ea |
#7b30d0 |
active indent guide, storage |
ember |
#f78c6c |
#da5221 |
added: the orange Neovim UIs expect |
red |
#ef5350 |
#de3d3b |
errors |
amber |
#ffca28 |
#9a6a00 |
warnings |
The light palette darkens a few original colors slightly (marked [adj] in
lua/winteriscoming/colors/light.lua) so code stays readable on white.
aerial, alpha, avante, barbar, blink.cmp, blink.pairs, bufferline, coc.nvim, codecompanion, codediff, copilot, dashboard, diffview, dropbar, fidget, flash, fzf-lua, git-conflict, gitsigns, grug-far, harpoon, headlines, hlargs, hop, hover.nvim, indent-blankline, lazy.nvim, leap, lspsaga, markview, mason, mini (animate, clue, cursorword, diff, files, hipatterns, icons, indentscope, jump, pick, starter, statusline, surround, tabline), minuet-ai, neo-tree, neogit, neotest, noice, nvim-cmp, nvim-cursorword, nvim-dap, nvim-dap-ui, nvim-navic, nvim-notify, nvim-scrollbar, nvim-tree, nvim-treesitter-context, nvim-ufo, octo, oil, orgmode, outline, overseer, rainbow-delimiters, render-markdown, sidekick, snacks (dashboard, picker, notifier, indent, input…), telescope, todo-comments, trouble, vim-gitgutter, vim-illuminate, virt-column, which-key, yanky.
With lazy.nvim or vim.pack (Neovim 0.12+), only the integrations for plugins
you have installed are loaded. Without either, all of them are.
Matching themes for other tools are in extras/, one file per style
(winteriscoming_blue, winteriscoming_black, winteriscoming_light). Each
tool's folder has a README with full setup steps:
| Tool | Setup |
|---|---|
| Alacritty | extras/alacritty |
| bat | extras/bat |
| btop | extras/btop |
| delta | extras/delta |
| eza | extras/eza |
| fish | extras/fish |
| foot | extras/foot |
| fzf | extras/fzf |
| Ghostty | extras/ghostty |
| Helix | extras/helix |
| iTerm2 | extras/iterm |
k9s (plus _transparent skins) |
extras/k9s |
| kitty | extras/kitty |
| lazygit | extras/lazygit |
| st | extras/st |
| Sublime Text (the bat themes) | extras/bat |
| Termux | extras/termux |
| tmux | extras/tmux |
| Vim | extras/vim |
| WezTerm | extras/wezterm |
| Windows Terminal | extras/windows_terminal |
| Xresources | extras/xresources |
| Yazi | extras/yazi |
| zathura | extras/zathura |
| Zed | extras/zed |
| Zellij | extras/zellij |
| Zettlr | extras/zettlr |
Looking for a font to go with the theme? See the font guide.
Regenerate them after changing the palette:
nvim --headless --clean -u NONE --cmd "set rtp^=." -l lua/winteriscoming/extra/init.luanvim --headless --clean -u NONE --cmd "set rtp^=." -l tests/smoke.lua
nvim --headless --clean -u NONE --cmd "set rtp^=." -l tests/extras.luaThe smoke test loads all three styles with every integration, checks every link
target and color value, background switching, italics = false, faithful,
transparency, the cache, overrides, plugin detection, every option, and the
lualine themes. The color options are held to measured invariants: WCAG AA for
contrast = "high" and rainbow_variables, simulated color vision separation
for colorblind, unchanged contrast under saturation. The extras test checks
the newer extras against each tool's own key list (tests/fixtures/ for Helix,
Zed and Yazi, each pinned to an upstream commit), compiles the st header and
loads the Vim colorschemes in Vim when cc and vim are installed.
CI runs both on Neovim stable and nightly, checks formatting with StyLua, lints Python with ruff, and fails if the generated extras are out of date. A weekly security workflow runs gitleaks and zizmor.
Releases come from conventional commits: feat is a minor release, fix and
perf a patch, ! or BREAKING CHANGE: a major, anything else none.
.github/workflows/release.yml opens a chore(release): vX.Y.Z PR that bumps
M.version, pyproject.toml and the CHANGELOG, and tags the commit once it
merges. Don't edit versions or CHANGELOG headings by hand.
The site at site/ is built into _site/ with
nvim --headless --clean -u NONE --cmd "set rtp^=." -l scripts/build_site.lua
and deployed by .github/workflows/pages.yml; its colors come from the real
palettes. Types for lua-language-server live in
lua/winteriscoming/types.lua.
The README images are rebuilt by scripts/screenshots/run.sh. It drives a real
LazyVim session through nvim --embed, borrowing plugins, treesitter parsers
and language servers from an existing LazyVim install, and needs uv and
JetBrains Mono Nerd Font. See the top of the script for overrides.
winteriscoming.nvim stands on the shoulders of:
- John Papa, creator of Winter is Coming for VS Code. The palette is his; this port only adds the extra shades Neovim needs and nudges a few colors (see Adjusted colors).
- Sarah Drasner: Night Owl, whose deep navy inspired the Dark Blue background, and the source of the orange this port adds.
- folke: tokyonight.nvim, whose architecture (plugin auto-detection, caching, extras) this plugin follows.
- Catppuccin:
catppuccin/nvim, the reference for
integration breadth and the
italics/boldswitches.






