Blog · Accessibility & Settings

Dyslexia and browser zoom - is bigger text always better?

10 min read · August 4, 2026

Ctrl+Plus is one of the first things a dyslexic reader discovers. It works instantly, requires no extensions, and makes every page feel more spacious. But zoom at 150% can push navigation menus off-screen, collapse sidebars, and turn a clean article into a landscape of horizontal scrolling. And zoom at 200% - something many readers with low vision genuinely need - breaks a surprising number of sites entirely.

Bigger is often better for dyslexic readers, but the way you get bigger matters. This article looks at how browser zoom actually works, when it helps, when it hurts, and what to do when it isn't enough.

What browser zoom actually does

When you press Ctrl+Plus (or Cmd+Plus on a Mac) in Chrome, Firefox, or Edge, you're applying full-page zoom. The browser scales every element on the page - text, images, buttons, whitespace, the lot - by a fixed percentage. At 125%, a 16px paragraph becomes a 20px paragraph. At 150%, it becomes 24px. At 200%, it becomes 32px.

This sounds straightforward, but the scaling happens at the rendering layer, after the page's CSS has already run. The CSS says "this sidebar is 300px wide" - the browser then scales that 300px by your zoom factor. On a typical 1440px-wide screen, zooming to 150% means the browser treats your screen as if it were 960px wide. Many websites have a tablet layout that kicks in at around 768px, so at 150% you'll often see a mobile-style single-column layout that's actually more readable. At 200%, however, a 720px virtual width hits most sites' minimum breakpoints and things can collapse or overflow horizontally.

Firefox and older versions of Internet Explorer also supported text-only zoom (View > Zoom > Zoom Text Only in Firefox), which increases font sizes without scaling images or layout elements. Text-only zoom is more surgical but also more likely to break layouts, because the text outgrows boxes that were sized for a smaller font. Chrome deliberately removed text-only zoom in favour of full-page zoom, which is why this option no longer appears in Chrome's menu.

Why dyslexic readers find zoom helpful

There are at least three distinct reasons zoom helps, and they're worth distinguishing because they point to different solutions.

Larger letter forms are easier to discriminate

Many dyslexic readers experience difficulty with letter discrimination - the visual process of telling a b from a d, or an m from an n at small sizes. When letters are physically larger, the differences between similar shapes are harder to overlook. At 13-14px - still the default on a surprising number of sites - the stroke difference between a lowercase b and d can be just a few pixels wide, which is genuinely ambiguous at normal reading distance.

Larger text creates more line spacing by default

Most sites set line-height as a ratio - typically 1.5 or 1.6 times the font size. When you zoom in and the font grows, the line height grows proportionally. A 16px font at 1.5x line-height gives you 24px between baselines. At 150% zoom that becomes a 24px font with 36px between baselines - a meaningful improvement for readers who lose their place between lines. If you've read our article on line spacing and letter spacing for dyslexia, you'll recognise this as the single most impactful typographic variable for dyslexic reading.

More zoom often means fewer characters per line

At 100%, a wide desktop column might hold 90-100 characters per line - well above the 60-70 range that most reading research identifies as optimal. Zooming in narrows the effective line length without requiring any changes to the site. The eye makes fewer jumps and is less likely to land on the wrong line on the return sweep. See our piece on line length and dyslexia for more on why 60-70 characters is the target.

When zoom makes things worse

The problems with full-page zoom are real, and they multiply at higher zoom levels.

Fixed-width elements that don't scale gracefully

Some sites lock elements at fixed pixel widths rather than using responsive design. A navigation bar hard-coded to 1200px wide doesn't care what your zoom setting is - it will overflow the viewport and trigger horizontal scrolling. Reading an article at 150% while the nav juts out 100px to the right is exhausting. Horizontal scrolling is particularly disorienting for dyslexic readers, who already expend extra effort tracking their position on the page.

Responsive breakpoints trigger unhelpful layout changes

Zoom tricks the browser into thinking the screen is smaller. At a certain zoom level you'll cross a breakpoint the site's designers intended for tablet users, and the layout shifts - sometimes helpfully (single-column, less clutter) and sometimes disruptively (menus hidden behind a hamburger icon, tables collapsed into something unreadable). The jump from 125% to 150% can transform a readable layout into an unusable one on sites that weren't designed with zoomed desktop users in mind.

Interactive elements and forms can break

Forms are especially vulnerable at high zoom levels. Dropdown menus may extend beyond the visible area. Date pickers often become unusable. On forms that dyslexic readers already find challenging, adding layout breakage on top creates a compounding problem.

Setting a permanent per-site zoom in Chrome

One underused Chrome feature: per-site zoom levels are remembered automatically. If you press Ctrl+Plus on a site, that setting persists across sessions for that domain. You don't have to zoom every time you visit - Chrome saves it. You can review and clear per-site zoom overrides at chrome://settings/content/zoomLevels.

This is useful if you have a handful of sites you visit daily with consistently small text. Set them once and forget about it.

Chrome's minimum font size setting

Less well known than zoom, and often more useful for dyslexic readers who don't want to distort layouts: Chrome's minimum font size. You can find it at chrome://settings/fonts - scroll to the bottom and set a minimum font size in pixels. Any CSS that tries to render text smaller than your minimum will be silently overridden.

The default minimum is 0 (disabled). Setting it to 14px or 16px prevents sites from using tiny captions, footnotes, or form labels - the specific text that most often trips up dyslexic readers - without touching the main body copy size or the overall layout. This is far less disruptive than global zoom because it only intervenes when text would have been too small, leaving everything else at its designed size.

The caveat: a minimum font size doesn't help with text that's already at 16px but set in a tightly-spaced, low-contrast font. It solves the size problem, not the shape problem. For font shape - swapping a site's font to Lexend, Atkinson Hyperlegible, or OpenDyslexic - you need a different tool.

Zoom vs font override: which to use when

These two approaches solve different problems. Here's a practical way to think about them:

Zoom handles size. Font overrides handle shape. They're complementary - many readers use both, running a font extension at 120-125% zoom. See our comparison of reader mode and reading extensions for more on when each approach fits.

What "optimal size" actually means for dyslexic readers

The dyslexia research on font size is less definitive than you might hope. Most practitioners recommend 18-20px for body text aimed at dyslexic readers - roughly what you'd get at 112-125% zoom on a typical site that uses 16px as its base. But optimal size is partly personal and partly task-dependent.

Reading a long article calls for different sizing than scanning a navigation menu. Proofreading your own writing - where the eye constantly backtracks - benefits from larger text more than skim-reading a summary does. Reading on a screen 60cm away is different from reading on a laptop 40cm away. A zoom level that works on a 27" desktop monitor may be excessive on a 13" laptop where 125% already shortens lines to a comfortable width.

The practical recommendation: start at 125% on sites you read regularly and adjust from there. If you find yourself losing your place between lines, try 150% and see whether the layout breaks enough to be annoying. If the shape of letters is the main issue rather than the size, zoom won't fix it - that's where a font-override extension like LexiFont does the work instead.

Firefox's text-only zoom - still worth knowing

Firefox's text-only zoom (View > Zoom > Zoom Text Only, then Ctrl+Plus) enlarges text without scaling images or layout elements. Because it operates at the CSS level - effectively increasing all em-based font sizes - it's less likely to trigger responsive breakpoints than full-page zoom. On a complex site where full-page zoom at 130% breaks the navigation, text-only zoom at 130% may leave the layout intact while still enlarging the body copy.

The trade-off: text-only zoom is more likely to cause text to overflow its container, because the boxes were sized for smaller text. On well-built sites using fluid layouts this is rarely a problem. On legacy sites with fixed-height containers, you may see text clipped or overlapping. It's worth testing on sites you read regularly. You can read more in our guide to Firefox for dyslexic readers.

Zoom on mobile - a separate question

On mobile browsers, pinch-to-zoom is available but behaves differently from desktop zoom. It scales a rendered page rather than re-rendering at a new zoom level, so the layout doesn't reflow - you get a larger version of the same layout, which usually requires horizontal scrolling. On iOS, Safari's Reader View is a far more effective tool for dyslexic mobile readers than zoom: it strips the page to text and lets you control font size, font choice, and background colour. Our mobile reading guide for dyslexia covers this in detail.

The honest answer: zoom is a blunt instrument

Browser zoom is available everywhere, costs nothing, and requires no setup. For many dyslexic readers it's the first and most effective thing they find. But it solves exactly one problem - text that is physically too small - and introduces layout friction that scales with the zoom level.

For readers whose main difficulty is letter discrimination (confusing similar letterforms rather than struggling with small print), zoom provides little benefit at the cost of broken layouts. For readers whose main difficulty is tracking across long lines, zoom helps by accident - it shortens lines, but reader mode does the same job without distorting the rest of the page.

Used in combination with a font override, zoom becomes genuinely powerful: you get letters that are both large enough to discriminate clearly and redesigned to be harder to confuse. LexiFont Pro pairs dyslexia-optimised fonts with per-site persistence, so you get the font-and-size combination that works for each site without resetting it on every visit.

Neither zoom nor font overrides are a complete solution alone. The useful question isn't "should I zoom?" but "what specifically makes this page hard to read?" - because the answer points to the right tool.

Further reading

• Best font size for dyslexic adults - what the research says
• Line spacing and letter spacing for dyslexia - what actually matters
• Line length and dyslexia - why column width is the first thing to fix
• Firefox settings for dyslexic readers - a complete guide
• Reader mode vs reading extensions - which works better for dyslexia?
• Reading on mobile with dyslexia - iPhone, Android, and iPad