Dark Omarchy themes: compare contrast, color and application consistency
Build a useful dark-theme shortlist, test secondary text and focus, and troubleshoot terminal, editor and wallpaper differences.
Based on public documentation; not hardware-tested. Match the instructions to your version and hardware.
Dark themes differ in more than the wallpaper: surface brightness, text tone, selection and accent colors all affect what you can distinguish. A nearly black desktop and a green-gray editor may both be called dark while looking and behaving very differently.
Use the gallery’s dark filter to see real images. The official theme manual remains the source for normal selection. This page helps narrow the choice and evaluate the working surfaces the pictures do not establish.
Choose a comparison group
Section titled “Choose a comparison group”| Direction in the reviewed palettes | Candidate | Background | What to inspect |
|---|---|---|---|
| Pastel on blue-gray | Catppuccin | #1e1e2e |
Selection and colored terminal output |
| Warm brown-gray | Gruvbox | #282828 |
Editor/terminal differences and muted text |
| Green-gray | Everforest | #2d353b |
Comments and boundaries between nearby surfaces |
| Dark ink-like gray | Kanagawa | #1f1f28 |
Bright text versus subtle selection |
| Restrained near-black | Matte Black | #121212 |
Inactive controls and window focus |
| Black baseline | Vantablack | #000000 |
Dark secondary elements against black |
These descriptions are comparisons of palette values, not measurements of battery savings or visual comfort. Black pixels’ power behavior depends on panel technology; this guide has not measured your display. Choose using readability and the task first.
Use one reproducible work scene
Section titled “Use one reproducible work scene”Open your normal terminal, an editor with the same code and a browser document. Keep font, scale, transparency, brightness and window dimensions unchanged. Choose two candidates from different groups rather than ten visually similar screenshots.
For each, answer:
- Can you read comments, timestamps and a disabled control when you need them?
- Does a selected line remain readable when it contains blue or yellow text?
- Can you identify the active window while two terminals show similar content?
- Does a search match stand out from both selection and error highlighting?
- Does the normal browser page still feel usable when moving from a dark editor?
Record the answer as a surface and symptom. “Inactive tab disappears” leads to a specific investigation. “Need more contrast” without naming text, selection or borders can lead to changing the wrong color.
Transparency changes the comparison
Section titled “Transparency changes the comparison”A translucent terminal combines foreground colors with the wallpaper behind it. A busy bright area can make the same palette seem inconsistent across windows. First compare with a stable, quiet background and your usual opacity; then assess a different image. If opacity was customized, test an opaque window before blaming the theme.
The wallpaper does not supply editor highlight groups. Likewise, changing monitor color temperature changes the whole rendered screen, not the theme’s stored hexadecimal palette. Keep those variables separate while diagnosing. Use window appearance and wallpapers for their respective settings.
If one application disagrees
Section titled “If one application disagrees”The pinned pipeline generates application files and uses different integration mechanisms. An editor colorscheme, GTK preference and website dark-mode setting are different layers.
| Difference | First useful check |
|---|---|
| Terminal is light, shell is dark | Fresh terminal, include path and personal terminal overrides |
| Neovim uses the old scheme | Active colorscheme, personal plugin settings and integration output |
| File manager is dark but not the same hue | GTK integration is not a guarantee of complete palette matching |
| Website is white | The website/browser controls that page’s appearance |
| Desktop is correct, boot unlock differs | Separate Style → Unlock configuration |
Do not install a browser extension or reset an editor simply because a screenshot shows matching colors. Decide whether you want palette identity, a common light/dark preference, or only legible applications. Follow application theming for a concrete trace when a supported integration fails.
Keep the final choice maintainable
Section titled “Keep the final choice maintainable”Record the selected theme and why it wins on your real content. Keep durable tweaks in personal theme/template or application configuration, with a saved original. Generated current-theme output is not the permanent editing layer in the pinned layout.
After a tweak, compare a second theme: a hardcoded background can make future switching appear broken. Revert the personal change and reselect the original if needed. For a custom black or dark community theme, check its repository and compatibility rather than treating its name as a quality claim. If a dark desktop does not suit your working environment, compare the same task with light themes instead of trying to force every surface darker.