Getting One Dark Window Working Across Your Editors
I've been using the One Dark color scheme as my default for years now. It started as the Atom default theme and got ported to everything—VS Code, Sublime, iTerm, Terminal.app, even Slack and Discord at some point. People still ask me about it because it's everywhere but rarely consistent across tools. Here's how to actually get it right. One Dark Window Summary is essentially a description of the One Dark color palette and how it maps to syntax highlighting, UI elements, and terminal colors across different applications. The original palette was designed by the Atom team around 2014 with five core tones: a deep nearly-black background, a slightly lighter panel background, muted gray-blue for text, a vivid green for success states, and a warm orange-red for errors. The "window" part usually refers to the sidebar/tab strip contrast against the main editing area. The problem most people run into is that every tool calls it something slightly different. VS Code calls it "One Dark." iTerm profiles call it "One Dark (iTerm)." Terminal emulators like Alacritty and Kitty have their own variants. The hex values shift by a few digits depending on who remixed it. This matters less for basic usage but becomes annoying if you're trying to keep your desktop consistent.
Installation and Configuration
I'll walk through the three places you actually need this: a code editor, your terminal, and maybe a browser dev environment. Open the extensions marketplace, search for "One Dark," and pick the one by Atom Community or similar. Install it. Go to File > Preferences > Color Theme and select One Dark. That's the easy part. The thing nobody tells you is that the raw One Dark theme doesn't handle newer VS Code UI elements properly—chat panels, command palette backgrounds, and the new sidebar toggle colors all look slightly off because the theme hasn't been updated for VS Code's 2024 UI overhaul. The workaround I use is combining the base One Dark theme with the "One Dark Pro" extension instead. One Dark Pro is a community fork that patches those UI elements and keeps the palette closer to the original intent. You also want to enable the "One Dark Pro Flavors" addon if you ever need a slightly blue-shifted or purple-shifted variant for different moods.
Terminal Emulators
For the terminal, you're working with 16-color or 256-color palettes now. The modern approach is using 24-bit true color with a proper .config file. For ZSH or Bash users, the sainnhe/one-dark-terminal repository on GitHub has scripts for iTerm2, Terminal.app, Alacritty, Kitty, and WezTerm. Alacritty configuration is the simplest—you drop the alacritty.toml file into ~/.config/alacritty/ and you're done. Kitty uses a .kitty.conf entry. iTerm2 requires importing the profile through Preferences > Profiles > Colors > Color Presets > Import. Here's where I hit a real snag: the iTerm2 import sometimes duplicates the One Dark profile every time you run the script because the import function doesn't check for existing names. I solve this by scripting a deletion of any profile containing "One Dark" before running the import. It's a known bug in iTerm2's import logic.
Get the Full Details
Browser Dev Tools
If you're doing frontend work, the Chrome DevTools theme extension "One Dark for DevTools" by Matt DesLauriers is the standard. Install it from the Chrome Web Store. After installation, go to chrome://settings/appearance and select One Dark from the developer tools theme dropdown. The caveat here is that this only changes the DevTools UI, not the actual page preview or Elements panel colors in newer versions of Chrome. The Extensions API for DevTools themes was deprecated in Chrome 112, so anything after that point requires you to use a separate extension like "One Dark Theme for DevTools" that uses a content script approach instead of the native API. Once you have the base installed, the real tuning happens. The default One Dark palette is fine out of the box, but most people tweak it without realizing why. The biggest lever is the foreground color. The original uses a gray-blue rather than pure white (#abb2bf). This is intentional—it reduces contrast and eye strain for long sessions. But if you have a 4K monitor or sit three feet from your screen, it can feel washed out. I bump it to #d4d7dc and save it as a custom variant. You can do this in VS Code by creating a custom theme JSON file based on One Dark's structure and overriding just the foreground token. The tokens you care about are "foreground," "text" in the scope definitions, and "editor.foreground" in settings.json.
Another thing beginners miss is that the gutter and minimap colors are separate from the main background. In One Dark, the gutter (#282c34) is a few shades lighter than the main background (#282c34)—actually, they share the same value, which means the gutter blends into the editor area. Some people prefer a subtle separator, so I add a 2px border with the same background color to the minimap wrapper and set the gutter background to #252a30 in VS Code settings. It's a tiny change but it makes line numbers easier to parse visually. If you're using a terminal multiplexer like tmux, you need a separate configuration. The .tmux.conf line for One Dark is: set -gq default-terminal "tmux-256color" and then source the color palette file. Without the tmux-256color flag, your pane borders and status bar revert to the system default colors and everything looks broken.
Common Pitfalls
The most frustrating issue I see people hit is theme conflict. If you have multiple themes installed—say One Dark for the editor and a different one for the terminal—and they don't share the same accent colors, your whole workspace looks disconnected. Green works for success indicators in the editor but the terminal uses cyan for the same semantic meaning. The fix is picking a single palette source and applying it consistently, or accepting the inconsistency and documenting it. Another pitfall: copying One Dark hex values from a blog post instead of the official repository. The palette has been remixed so many times that random GitHub gists contain variations with slightly different greens or oranges. The official Atom One Dark repository on GitHub at https://github.com/atom/one-dark-syntax is the source of truth. Anything else is a derivative. Performance-wise, One Dark has zero overhead. It's a static color set. Some people report that custom theme JSON files slow down VS Code startup if they have complex color rules, but the standard One Dark theme loads instantly.
Alternatives Worth Knowing About
If One Dark doesn't work for you, the closest alternatives are One Dark Vivid (higher saturation, better for colorblind users who confuse green and blue), Night Owl by Sarah Drasner (bluish tint, designed for low-light coding specifically), and Everforest (warmer, brownish-green tones that reduce blue light exposure). Everforest is probably the best direct competitor if you find One Dark too cool-toned. There's also the practical consideration that some tools just don't support custom themes well. Obsidian handles One Dark through community themes. Notion doesn't support dark themes natively yet, so that's a non-starter. JetBrains IDEs have their own One Dark plugin in the marketplace, but the intellij platform theme system is picky and sometimes overrides the syntax colors with its own defaults.
Where to Download
VS Code: Search "One Dark Pro" in the extensions marketplace. Extension ID: zhuangtongfa.material-theme is the broader suite if you want additional material-style variants. iTerm2: sainnhe/one-dark-terminal on GitHub. Clone the repo, run the install script for iTerm2. Alacritty: Same repository, different config file. Copy alacritty.toml to ~/.config/alacritty/.
Kitty: Use the kitty.conf snippet from the same repo, add the include directive to your ~/.config/kitty/kitty.conf. Browser DevTools: "One Dark Theme for DevTools" on the Chrome Web Store. JetBrains: Plugin marketplace, search "One Dark" or use the Material Theme UI plugin which includes One Dark as a variant.
A Quick Note on Consistency
After you've installed the theme everywhere, spend ten minutes reviewing each tool's appearance. Check the sidebar, the tab strip, the scrollbars, the error underlines, the active line highlight. You'll spot the mismatches quickly. The green from your terminal might be slightly more lime than the green in your editor. That's normal. You'll either adjust it or stop caring after a week. I still notice the mismatch between my terminal green and my VS Code green, but I've decided it's fine. The One Dark palette works because it's deliberately desaturated. It's not trying to be bold. It's designed to sit in the background while you read code. That's why it's lasted this long across editor ecosystems. Most dark themes are too high contrast or too saturated. One Dark stays out of the way.
