Dark Mode vs Light Mode — Which Is Easier on the Eyes?

health/dark-mode-vs-light-mode-eye-comfort · Updated 2026-09-23 · Tags: health, ux, display, eye-strain, accessibility

Dark Mode vs Light Mode — Which Is Easier on the Eyes?

Colour key: Light mode Dark mode Auto-switch

TL;DR

Neither mode is better for your eyes. Neither damages them, and neither prevents eye strain — that comes from not blinking, not from colour.
Light mode is easier to read; dark mode is easier to sit in when the room is dark. That is the whole trade-off.
Skip dark mode if you have astigmatism (~30–47% of people) — bright text on black glows and smears.
Developers are the exception, but that is VS Code's default talking, not eye health.
Verdict: don't choose — switch automatically. Light by day, dark after sunset, brightness matched to the room, text one size bigger. Editor setup under If you code all day.

The short answer to "is dark mode better for my eyes over long usage?"

Two different questions get tangled together here, and they have different answers:

Question	Answer
Does dark mode prevent long-term eye damage?	No. Neither mode damages your eyes. There is no evidence that screen polarity or blue light causes eye disease.
Does dark mode reduce digital eye strain over a long session?	Only indirectly, and only sometimes — by lowering total light output in a dim room. In a bright room it can make strain worse.
Is dark mode more comfortable?	For most people, in a dark room, yes. In a bright room, no. It is a lighting question, not a preference question.
Is dark mode easier to read?	Generally no. Light mode measures better for reading performance.

Anyone telling you one mode is universally "better for your eyes" is overselling the evidence in both directions.

Where light mode wins

Legibility and reading performance

This is the most consistent finding in the literature, and it has been replicated for decades. Dark text on a light background — positive polarity — beats light-on-dark on visual acuity tasks, proofreading accuracy and reading speed. Nielsen Norman Group's review of the evidence found light mode won across all dimensions tested, for both younger and older adults.

The mechanism is straightforward optics:

A bright background makes your pupil constrict.
A smaller pupil gives you a greater depth of field and reduces the effect of optical aberrations in your own eye.
Result: sharper edge definition on small type.

The corollary matters: the smaller the text, the bigger light mode's advantage. For 11px UI labels and dense body copy, this is a real effect. For a 28px headline, it mostly vanishes.

Long-form comprehension

For articles, PDFs, documentation and anything you read to understand rather than scan, light mode has the edge. This is partly optics and partly 500 years of habit — we learned to read on paper, which is positive polarity.

It's what most content is designed for

Forced dark mode (browser extensions, OS-level inversion) frequently produces low-contrast text, invisible borders, blown-out images and unreadable syntax highlighting. Purpose-built dark themes are fine; automatically inverted ones often are not.

Where dark mode wins

Dim and dark rooms

This is dark mode's strongest and least disputed case. A bright white page in a dark room is a small lamp pointed at your face. The mismatch between screen luminance and ambient luminance is what causes discomfort glare, and it forces your pupils to keep readjusting between the screen and the dark surroundings. In that setting dark mode is genuinely more comfortable, and the survey data reflects it — around two-thirds of users report preferring dark mode specifically for low-light comfort.

Photophobia and light sensitivity

For people with migraine, concussion recovery, uveitis, dry eye or general light sensitivity, less emitted light is a real benefit. This is a legitimate accessibility use case, not a preference.

Blink rate — a 2025 finding

A 2025 study of tablet users over one continuous hour found dark mode produced a higher blink rate and better pupil accommodation — both markers of less visual fatigue. The twist: the same participants subjectively reported less fatigue in light mode and preferred it, which the authors attribute to lifelong habituation to dark-on-light text.

That gap is the single most interesting result in this area. What feels easier and what measures easier are not the same thing. Be sceptical of your own preference as evidence — and be equally sceptical of a single 30-person study.

Myopia — the counter-intuitive one

Most people assume dark mode is the "unhealthy" choice. One well-cited 2018 study (Aleman, Wang & Schaeffel, Scientific Reports) found the opposite signal:

Reading dark text on bright background for one hour overstimulated retinal OFF-pathways and caused choroidal thinning — a precursor associated with myopia progression.
Reading inverted contrast (dark mode) stimulated ON-pathways and caused choroidal thickening — associated with myopia inhibition.

The effect appeared at book-sized letters (0.5°) and not at phone-sized letters (0.25°). And choroidal thickness is a short-term proxy, not a measured long-term refractive outcome. Some clinicians have started recommending dark mode for myopia control on this basis; it is suggestive, not settled.

OLED battery and true black

On OLED and AMOLED panels, black pixels are switched off. Real power savings, no eye-health claim attached.

Where dark mode actively hurts: halation

If you take one practical thing from this doc, take this one.

Halation is the glow or bleed you see around bright text on a dark background. Your pupil dilates to cope with the dark field, then bright glyphs overstimulate the retina, and letters appear to smear or trail — especially while scrolling.

It is worst for people with astigmatism, which is roughly 30–47% of people, many of them undiagnosed or under-corrected.
Symptoms: text looks fuzzy or "glowing", words seem to vibrate, and long sessions produce headaches rather than simple tiredness.
It is maximised by pure white on pure black — the exact combination most naive dark themes ship with.

Fixing it

Do	Don't
Background around `#121212`–`#282828` (RGB 30–40)	Pure black `#000000`
Text around `#DCDCDC` (RGB ~220), or white at ~87% opacity	Pure white `#FFFFFF`
Slightly heavier weight or larger size than the light theme	Reuse the light theme's thin weights verbatim
Keep contrast within WCAG AA, but do not maximise it	Chase the highest contrast ratio available

Light text on dark optically "blooms" and looks thinner, so a font weight that reads correctly in light mode often reads spindly in dark mode.

Why developers overwhelmingly use dark mode

Developer dark-mode use sits far above the general population: 77% in 2018 and 83% in 2019 on JetBrains' State of Developer Ecosystem survey, and stable since. Against everything above, that looks like a contradiction. It mostly isn't a vision finding — it's three separate things stacked.

1. It's the default, and almost nobody changes a default

VS Code has shipped a dark theme as its default since launch in 2015 (Dark+, now Dark Modern). Cursor is a VS Code fork and inherits it. More tellingly, window.autoDetectColorScheme is false by default — a fresh install stays dark even when the OS is set to light. The editor takes a position rather than following you.

The lineage runs backwards from there. Visual Studio 2012 was the first VS to ship a dark theme out of the box, and it was popular enough that Dark+ is essentially "Dark (Visual Studio)" with extras. VS Code's 2015 competitors defaulted dark too — Sublime Text to Monokai, Atom to One Dark. By then dark simply was the convention for a code editor.

Microsoft has never published a rationale for the choice. Read it as path dependence and product identity, not ergonomics.

2. Syntax highlighting has more usable colour space on dark

This is the one real technical advantage, and it is specific to code.

Saturated hues — cyan, violet, lime, orange — reach comfortable contrast against a #1E1E1E background easily. Against white you have to darken and desaturate every token colour to keep it legible, and hue separation collapses: everything drifts toward muddy navy and maroon. A dark theme gets more perceptually distinct token colours for free. Put Dark+ and Light+ side by side and the light variant is visibly the derived one.

3. Code is not prose, and the session is long

Light mode's legibility advantage is largest on small, dense, continuous text. Code is sparse, short-lined, heavily indented, and scanned rather than read linearly — so the strongest argument for light mode is at its weakest here. Add 8–10 hour sessions across one or two large monitors, where total emitted light scales with screen area × time, and the comfort maths tilts.

All of this explains popularity, not superiority. "83% of developers use dark mode" is mostly a fact about a default. And the 30–47% with astigmatism are inside those dark themes too, often fighting halation all day without naming it — 13px monospace at thin weights is close to the worst case for it. Which is exactly why #D4D4D4 text on #1E1E1E is a far better default than the pure-black themes people install from the marketplace.

What actually causes eye strain (and it isn't the colour scheme)

Digital eye strain is real, but its causes are mechanical and behavioural:

Reduced blinking. Normal blink rate is 15–20/min; it roughly halves while you focus on a screen. This is the main driver of the burning, gritty, dry sensation.
Sustained accommodation. Hours of near-focus without relief fatigues the ciliary muscle.
Uncorrected or wrong prescription. Astigmatism and presbyopia show up as screen strain long before you notice them elsewhere.
Brightness mismatch with the room — in either direction.
Poor ergonomics. Screen too close, too high, or a glare source behind you.

The American Academy of Ophthalmology's position is explicit: blue light from digital devices does not cause eye strain and does not cause eye disease, and they do not recommend blue-light-filtering glasses for it. Blue light does affect circadian rhythm — night-shifting your display helps you sleep, not your eyes. And note that dark mode's night benefit is mostly about less total light, not about colour temperature.

What to actually do

The high-leverage moves, in order:

Match screen brightness to your surroundings. This does more for comfort than the mode choice, in both modes. A useful check: your screen should look like a well-lit sheet of paper in the room, not a light source and not a grey smudge.
Get your eyes checked, especially if dark mode "hurts" — that pattern points at uncorrected astigmatism.
Blink deliberately and take breaks. The 20-20-20 rule (every 20 min, look 20 feet away for 20 seconds) is the standard advice. The specific numbers are not strongly evidenced, but "look away and blink regularly" is.
Increase text size before you change anything else. It helps in both modes and outperforms polarity tweaks.

Then choose the mode by context:

Situation	Use
Bright office / daylight, long reading	Light mode
Dim room, evening, night	Dark mode
Long-form reading and proofreading	Light mode (or sepia)
Code editing, dashboards, terminals	Dark mode is fine — large-ish monospace, and it's where syntax colour reads well (see If you code all day below)
Photophobia, migraine, light sensitivity	Dark mode, low brightness
Astigmatism, or text "glows" for you	Light mode, or a low-contrast dark theme (never `#FFF` on `#000`)

Put your OS on auto / scheduled switching — light during the day, dark after sunset — and stop treating it as a fixed choice. Sepia or warm off-white (like an e-reader) is an underrated middle option for long reading; it keeps positive polarity while cutting emitted light.

If you code all day

Auto-switch, dark-leaning. Let the editor follow the room instead of picking a side:

// VS Code / Cursor settings.json
"window.autoDetectColorScheme": true,
"workbench.preferredDarkColorTheme": "Default Dark Modern",
"workbench.preferredLightColorTheme": "Default Light Modern",
"editor.fontSize": 14               // one size up beats any polarity tweak

Then set the OS to automatic appearance (macOS: System Settings -> Appearance -> Auto) and both follow the sun.

Context	Use
Editor, bright room or daylight	Light — dense monospace is where light mode's edge is real
Editor, evening or dim room	Dark
Terminal	Dark always — scanned output, switching buys nothing
Docs, tickets, PDFs, long-form reading	Light
Text "glows" or smears for you	Light, and book an eye test

Any theme built on #000000 with #FFFFFF text, and browser "force dark" extensions, which wreck syntax highlighting and contrast on pages never designed for it.

If switching is more friction than it's worth, just stay dark. The cost is small for code specifically, and a consistent environment beats an optimal one you keep fiddling with.

If you build interfaces

Ship both, respect prefers-color-scheme, and let users override. Neither mode is correct for everyone.
Design the dark theme; don't invert the light one. Elevation via lighter surfaces rather than shadows, desaturate accent colours, re-check every contrast pair.
Avoid pure black backgrounds and pure white text. Consider bumping font weight slightly in the dark theme.

Bottom line

Over long sessions, light mode is easier to read and dark mode is easier to sit in when the room is dark. Your eyes are not being damaged either way.

If you want a single default: light mode by day, dark mode at night, brightness matched to the room, text one size bigger than you think you need, and a break every 20 minutes. That combination beats any amount of arguing about polarity.

Sources

Disclaimer: These documents are personal notes. The information may be incomplete, out of date or wrong, so check it before you rely on it.