Microsoft Edge's Read Aloud feature is free, built into a browser most Windows users already have, and genuinely good for what it's designed to do. It's also the subject of a specific, recurring complaint: PDFs. If you've had a PDF restart from page 1 when you tried to resume it, or watched the highlighted word drift away from what's actually being read, this is about exactly that problem, and what to do instead.
What Edge Read Aloud does well
Worth saying plainly first, since it's easy to only focus on the complaints. Edge Read Aloud costs nothing, requires no account, and needs no setup beyond having Edge installed, which most Windows machines already do. It reads web pages using Microsoft's natural sounding neural voices, with word or sentence highlighting synced to what's playing, and it does this well for the case it was built for: an article or page you're currently looking at, read aloud in the moment. For that specific, short, in-the-moment use, it's a genuinely solid free feature, not a stripped-down afterthought.
The PDF problem, as reported by users
The recurring issue shows up specifically with PDFs, not with regular web pages. Users have reported Edge's PDF playback restarting from page 1 when they try to resume a document they were partway through, rather than picking up where they left off. Others report loading hangs when opening or resuming a PDF in Edge's reader, and highlighting that falls out of sync with the audio, especially on longer or more complex PDFs, where the highlighted word or line drifts ahead of or behind what's actually being spoken.
None of this means Edge Read Aloud is broken for every PDF, every time. But it's a common enough pattern that if you're planning to listen through something long, a lengthy report, a research paper, a full chapter, it's worth expecting friction rather than assuming it'll work as smoothly as it does on a short web article. A feature that mostly works is a different thing than a feature you can rely on to track a 40-page document from start to finish across multiple sessions.
Why this happens more with PDFs than web pages
Web pages are structured text that a browser's reading tools can walk through fairly cleanly. PDFs are a different animal: they're often a fixed visual layout rather than clean, structured text, which makes accurately tracking position, and resuming exactly where you stopped, a harder problem in general, not just for Edge specifically. That's not an excuse for the reported bugs, but it explains why a feature built primarily for reading web pages runs into more trouble specifically with PDFs, where the underlying structure is messier to begin with.
When to just keep using Edge
If most of what you read aloud is web articles, not PDFs, there's no reason to look elsewhere. Edge Read Aloud handles that case well, for free, with no setup. Even for occasional PDFs, if they're short enough that a restart from page 1 costs you thirty seconds rather than ten minutes, it may still be the simplest option available. The issues described above are specifically a problem for longer PDFs you want to resume reliably across sessions, not a reason to abandon Edge for every use case.
When to move to a dedicated reader
The honest line is usage-based: if you're regularly listening to PDFs, especially longer ones, and losing your place or dealing with sync drift is actually costing you time and frustration, that's the point where a tool built specifically to handle documents, not just browser tabs, starts to pay for itself. The core difference is that a dedicated document reader treats a PDF as a document with a real position to track, rather than a page being read in the moment.
ReadLoud is one option built this way. It accepts PDF, EPUB, DOCX, HTML, Markdown, CSV, and plain text, along with pasted text and web links, up to 40 MB per file and 900,000 characters per document. PDFs specifically lose headers, footers, page numbers, and citation brackets during import, and whatever gets skipped is shown dimmed in the text, so nothing silently disappears without you knowing. Your position in a document, the exact sentence you stopped at, is saved to a library and synced across devices, so resuming means resuming, not restarting.
Word highlighting is measured from the actual generated audio using forced alignment against Google's speech recognition, rather than an estimate, which is the direct answer to the sync-drift problem reported with Edge's PDF playback. There's no subscription: 1 minute free with no account, 20 minutes free with a sign-up, then minute packs from $9 that never expire.
A side-by-side view
| Edge Read Aloud | ReadLoud | |
|---|---|---|
| Cost | Free, built into Edge | Pay per minute, no subscription |
| Web pages | Yes, its core strength | Yes, via link extraction |
| PDFs | Yes, with reported resume and sync issues | Yes, with position saved to a library |
| EPUB, DOCX, and other files | No | Yes |
| Position tracking across sessions | Reportedly unreliable on PDFs | Resumes at the exact sentence you stopped at |
| Works outside the Edge browser | No | Yes, any modern browser |
| Setup required | None | Free account for 20 minutes; none for the first minute |
The practical decision
Don't switch away from a free, built-in tool just because it exists to be replaced. Switch when the specific problem, a PDF that won't resume properly, or highlighting that drifts, is actually happening to you and actually costing you something. If that's where you are, try ReadLoud's free minutes on the same PDF that's been giving Edge trouble, and see whether reliable resume and synced highlighting are worth paying per minute for. Our comparison of Speechify and Edge Read Aloud covers a paid subscription option too, if you want the full range of choices in one place.