Blog · Reading workflows

Dyslexia-friendly PDF reading in Chrome

11 min read · April 29, 2026

PDFs are the worst common file format for dyslexic readers. The fonts are baked in, the lines don't reflow, the columns are fixed at the width of an A4 page, and many of them are scanned images of paper rather than real text at all. Worse, the trick that makes the rest of the web readable - installing a font-override extension like LexiFont and switching to OpenDyslexic or Lexend - does not work inside Chrome's built-in PDF viewer. This is the honest workflow for getting around that.

The short version

Why PDFs are harder than HTML

HTML was designed to flow. It assumes the device, the window size, the font, and the reader's preferences are all unknown - so the browser handles layout at the moment the page is rendered. That is exactly what makes the web fixable for dyslexic readers: the text is structured data, and any extension can re-style it.

PDF is the opposite. The format was designed by Adobe in 1993 to make a digital page look identical to a printed page on every device, forever. Each glyph is positioned at fixed coordinates. The font is embedded inside the file. Line breaks are baked. Columns are fixed. There is no semantic structure unless the author explicitly added it (and most do not).

For a dyslexic reader trying to apply the standard interventions covered in our other posts - a larger font size, looser line and letter spacing, a tinted background, a sans-serif typeface - none of these levers are available in a raw PDF. The page is a snapshot, and a snapshot does not stretch.

Why Chrome's PDF extensions don't help

The reason font-override extensions cannot reach into a Chrome PDF tab is structural. When Chrome opens a .pdf, it is not rendering HTML. It loads PDFium, an embedded PDF rasteriser, inside an isolated extension context. Content scripts injected by other extensions don't run there. The CSS you would normally apply to body or p simply has no targets, because there is no DOM in any meaningful sense. This is the same reason browser tools like Stylus, Dark Reader and Reader Mode also do not work inside an open PDF.

This is not a LexiFont limitation. It is true of every browser-extension approach to PDF styling, on every Chromium-based browser. The only way to apply dyslexia-friendly typography to a PDF is to either reflow it inside a reader that supports reflow, or convert it out of PDF entirely.

Path 1: Reflow the PDF in place

"Reflow" means rebuilding the document's text into a single column that wraps to whatever width the window has, abandoning the original page layout. Several tools do this. The two most reliable in 2026:

Adobe Acrobat Liquid Mode (mobile and web)

Adobe added Liquid Mode to Acrobat Reader in 2020 specifically for reading on small screens. It uses machine learning to recover the document's reading order, then re-renders it as flowing text with adjustable font size, spacing, and line height. The desktop browser version is more limited than the mobile app, but if you upload a PDF to Acrobat on the web at acrobat.adobe.com and open it in Liquid Mode, you get a sliders-based reflow view that handles most academic and business PDFs reasonably well. Scanned PDFs need OCR first - Acrobat will offer to run it.

Microsoft Edge Immersive Reader

Edge ships with a feature called Immersive Reader that handles PDFs natively. Open a PDF in Edge, click the book icon in the address bar, and the document is reflowed into a single column with explicit dyslexia-friendly options: a font picker that includes OpenDyslexic-style alternatives, line spacing presets, syllable splitting, line focus (only one or three lines visible at a time, the rest dimmed), background colour swatches, and a read-aloud function with sentence highlighting. This is the single best out-of-the-box dyslexia experience for PDFs in any browser. You can install Edge alongside Chrome on the same machine and use it only for PDFs - no need to switch your default browser.

Edge is a Chromium browser, so installed Chrome extensions can usually be moved across, but for PDFs the Immersive Reader is doing more than any extension can: it has privileged access to the rendered text content of the PDF that Chrome blocks for security reasons.

Path 2: Convert the PDF first

If you want to stay in Chrome and use the same reading setup you've already built for web pages - LexiFont, your tinted background, your preferred line height - the move is to convert the PDF to a format Chrome treats as text. Three options that work reliably in 2026:

Convert to HTML

The cleanest path. Tools like pdf.js-based converters and the open-source pdftohtml command produce a single HTML page from a PDF, with the original text content preserved as actual <p> elements. Once it's HTML, every dyslexia-friendly intervention is back on the table: font override, font size, line height, background tint, reader mode. This is the workflow most academic readers with dyslexia I've spoken to settle on for papers they'll read more than once.

Several browser-based converters do this without installing anything: pdftohtml.online, pdf2htmlEX-based services, and Adobe's "Export PDF" feature (which can export to HTML, though it tends to keep the original CSS and styling, which partly defeats the purpose - prefer "plain HTML" or "reflowed HTML" options where offered).

Convert to EPUB

EPUB is HTML in a wrapper. Calibre, the free desktop reader, has a robust PDF-to-EPUB converter that lets you set the target font, line height, page colour and margins during conversion. Once it's an EPUB, you can read it in any browser-based EPUB reader (epub.js demos, the Thorium Reader web app, or just a reading-mode extension pointed at the converted file) with full font control.

Convert to plain text and reformat

For a PDF where the layout is hopeless - multi-column scanned papers, court filings, badly OCR'd scans - the most reliable move is to extract the raw text with a tool like pdftotext (or any of the "PDF to text" web converters), paste it into a clean Google Docs or markdown file, and read from there. Our Google Docs setup post covers the typography settings that work once you're in Docs.

Scanned PDFs need OCR first

A meaningful fraction of PDFs in the wild - older academic papers, government forms, PDFs of paper books - are not text at all. They are images of text, sometimes at low resolution. None of the workflows above will work on a scanned PDF, because there is no text data to reflow or convert.

The fix is OCR (optical character recognition), which converts the image of text into actual text. Three options:

1. Adobe Acrobat's web service runs OCR automatically when you open a scanned PDF and ask for Liquid Mode or text editing.
2. The open-source Tesseract engine, wrapped in services like ocr.space, will accept a scanned PDF and return a text version in a minute or two.
3. If you only need a few pages, take a screenshot and paste it into Google Docs - Docs has built-in OCR on image uploads.

Once OCR has produced a text layer, every other workflow on this page becomes available. The OCR will have small errors, especially on numbers, equations, and proper nouns. For research where exact wording matters, double-check against the original.

Once it's reflowable, what to set

Whichever path you take to get the PDF into a flowing format, the typography settings to dial in are the same ones that work for any long-form reading:

The academic-paper recipe

Academic PDFs are the hardest case: dense, two-column, full of footnotes and equations, often locked behind a publisher's viewer. The workflow that has worked best for the dyslexic researchers I've corresponded with:

1. Download the PDF (don't read it inside the publisher's web viewer, which is even worse than Chrome's PDFium).
2. Open it in Edge with Immersive Reader for the first pass. This gets you reading order right, syllable splits where useful, and read-aloud if you want to skim by ear while your eyes follow.
3. If you'll come back to the paper, convert it once - to HTML or EPUB - and save the converted version. Re-reading is where the cumulative time savings live.
4. For equations and figures, fall back to the original PDF. Reflow tools mangle equations because they treat each glyph as a separate text run.

When to give up on the PDF

For papers and articles, the open-access HTML version - if one exists - is almost always a better read than the PDF. Sites like arXiv, bioRxiv, and PubMed Central host HTML alongside the PDF for most papers. Government agencies often publish a "web accessible" HTML version of the same document that is buried two clicks deeper than the PDF link. Spend thirty seconds searching for the title plus "html" before you commit to reading the PDF - the time savings are large.

For books, an EPUB or Kindle version is always preferable to a PDF. Both formats reflow, accept your font choice, and let you set spacing. Buying the same book twice (PDF for citation, EPUB for reading) is occasionally worth it for a book you'll spend hours with.

Where LexiFont fits

LexiFont applies dyslexia-friendly typography to every web page Chrome renders, but as covered above, it cannot reach inside Chrome's PDF viewer. Where it does work:

• Once you have converted a PDF to HTML and opened it in Chrome - LexiFont restyles it like any other page.
• On the publisher's article page (the HTML abstract or full text), where most of the time the PDF is just a download link.
• On EPUB readers that run as web pages, where the underlying renderer is HTML.

If you read a lot of PDFs, the honest recommendation is to keep Edge installed for the Immersive Reader, install LexiFont in Chrome for everything else, and treat conversion-to-HTML as a one-time investment for any document you'll re-read. LexiFont Pro adds Lexend, Atkinson Hyperlegible and Comic Neue to the free OpenDyslexic, which gives you four very different font shapes to test on a converted PDF before you commit to reading mode.

Further reading

• Best fonts for dyslexia in 2026 - a research-first guide
• Best font size for dyslexic adults - what the research really says
• Line spacing and letter spacing for dyslexia - what actually matters
• Background colours for dyslexia - cream, blue or grey?
• Dyslexia-friendly Google Docs setup