Press Ctrl and + (Cmd and + on a Mac) to enlarge a web page. Press Ctrl and - to shrink it, and Ctrl and 0 to return to normal size. A well-built page keeps working as you zoom. The text wraps, nothing overlaps, and you never scroll sideways to finish a line.

This page covers the shortcuts, the two kinds of zoom, and what the W3C accessibility rules ask of a page at 200% and 400%. It also gives fixes for the moment a page falls apart.

The fastest ways to zoom

The W3C says that in most browsers, Ctrl or Cmd with + increases zoom, with - reduces it, and with 0 resets it. Chrome's help page lists the + and - keys for Windows, Linux, Mac and Chrome OS.

ActionWindows and LinuxMac
Zoom inCtrl and +Cmd and +
Zoom outCtrl and -Cmd and -
Back to normalCtrl and 0Cmd and 0

You can also use the menu. In Chrome, open the More menu at the top right and find the Zoom line. It has buttons for zooming in, zooming out and full screen.

Chrome keeps the zoom level for each site. To see or clear those levels, open Settings, then Privacy and security, then Site settings, then Additional content settings, then Zoom levels. Menu names can differ by version.

Page zoom or text-only zoom?

Page zoom makes everything larger: text, images and controls. Text-only zoom changes just the size of the letters. WCAG lists both among the ways a browser can scale content, along with magnification.

In Chrome, both live under Settings, then Appearance. "Page zoom" changes everything. "Font size" changes the font only. Chrome warns that some websites do not let a browser change only the text size. On those sites the font setting does nothing.

Page zoomText-only zoom
What growsText, images, layoutText
Works on every siteUsuallyNo, some sites block it
Best forGoing past 200%Small, steady increases
Main riskWide layouts force sideways scrollingText can collide with boxes of fixed size

WCAG notes that above 200%, page zoom may work better than text resizing. At extreme sizes, words may be cut off, text may overlap other content, or a single word may fit on each line.

What the standards expect

WCAG 2.2 has two rules that matter here. Success Criterion 1.4.4 (Resize Text) asks that text can be enlarged up to 200% without loss of content or function. It excludes captions and images of text.

Success Criterion 1.4.10 (Reflow) goes further. Content should work without scrolling in two directions at a width of 320 CSS pixels. That equals a 1280 pixel wide window at 400% zoom.

Reflow has exceptions for parts that need a two-dimensional layout. WCAG names maps, diagrams, video, games, presentations and data tables. Ordinary paragraphs are not exempt.

The arithmetic is simple. A 1280 pixel window at 100% offers 1280 CSS pixels of width. At 200% it offers 640. At 400% it offers 320.

The reason is plain. When lines run past the edge of the screen, readers scroll back and forth to read each one. WCAG says this can make people lose their place and adds to the effort of reading.

A wide table is a fair example of an exception. A weekly timetable with seven columns may need to scroll in two directions. Even then, you can keep the first column and the header row clear, so the reader knows which row they are on.

Test a page in two minutes

You do not need a tool. The W3C easy check suggests a narrow browser window and the zoom keys.

  • Make the browser window fairly narrow.
  • Press Ctrl or Cmd with + five times. That should reach 200%.
  • Check that every line of text wraps inside the visible area.
  • Check that no text hides behind other text or an image.
  • Look for sideways scrolling on ordinary paragraphs.
  • Repeat at 400% with a wide window.

A menu that turns into an icon at large sizes is fine. The W3C check says so directly.

When a page breaks at high zoom

If you are the reader, try these in order.

  1. Go down one zoom step. Some layouts only fail at one size.
  2. Go up instead. Because the window shrinks in CSS pixels as you zoom, many pages switch to a narrow layout at 300% or 400%. That layout is built to reflow.
  3. Use the font-size setting instead of page zoom, if the site allows it.
  4. Open the page in reader view, which strips the layout away.

If you are the author, WCAG's Reflow page points to a single column as a common fix. It also warns that fixed or sticky bars can make reading hard at large sizes. Text inside images pixelates when scaled, so use real text.

If you write the words yourself, short paragraphs help at any zoom level, because each screen shows fewer lines. The Easy-Read Editor can help you tidy a draft before it goes on the page.

Common mistakes

  • Testing only at 100%. A page that looks fine at normal size can fail at 200%.
  • Putting text in images. Images do not wrap, and they blur when enlarged.
  • Fixing widths in pixels. A rigid box cannot follow the window as it narrows.
  • Blocking pinch zoom. See the phone text guide for why that is a problem on small screens.
  • Using zoom as the fix for tiny text. Start with a sensible font size so readers need less zoom.

FAQ

How do I go back to normal size?

Press Ctrl or Cmd with 0. In Chrome you can also use the Zoom line in the More menu and step back down.

Does my zoom change the page for other readers?

No. Zoom is a setting in your own browser. Chrome saves it per site on your device.

Is 200% the most a page must support?

No. WCAG asks for 200% as the text resize target. The Reflow rule goes to 400%, using a 320 pixel wide layout.

Why does a zoomed page start to look like a phone page?

Zooming shrinks the width available to the page, measured in CSS pixels. At 400% a 1280 pixel window offers 320 pixels. Pages that adapt to narrow screens switch layout at that point.

Sources

Each page below was opened and read on the date shown. Where a fact comes from one of them, the guide says so.

This guide gives general information about readability. See the Disclaimer. To report a mistake, use the Corrections page.