Microsoft Edge PDF reader
PDF reader built into Edge, with inking, highlighting, text notes and read aloud.
Operated by Microsoft
Opens the vendor's own site.
Jobs covered
Open a task to see exactly what the vendor documentation supports.
View
Browse all view toolsviewing PDF documents in the Microsoft Edge built-in PDF reader, where Microsoft Learn documents a reader that opens local pdf files, online pdf files and pdf files embedded in web pages and annotates them with ink and highlighting, scoped to the Windows and macOS desktop platforms, with a pin-able toolbar and basic reading and navigation features including zoom, rotate, fit to page or width, jump to page and search, plus a table of contents pane, page view, caret mode browsing, inking and ink customisation, highlight, text notes and read aloud; the same page documents basic form filling with JavaScript forms not supported, viewing Microsoft Purview Information Protection protected files within the same business tenant on Windows and macOS and across business tenants, viewing Information Rights Management protected files, keyboard accessibility, high contrast mode and screen reader support, and viewing and validating certificate-based digital signatures while saying Microsoft is actively working to address more signature scenarios; the documented constraints are that XML Forms Architecture (XFA) is a legacy format not supported in Microsoft Edge, with an enterprise option to view XFA PDFs in IE mode through the ViewXFAPDFInIEModeAllowedOrigins or ViewXFAPDFInIEModeAllowedFileHash policies; the reader is being replaced by a new built-in PDF reader powered by Adobe Acrobat, which Microsoft's policy documentation describes as the reader that the NewPDFReaderEnabled policy launches, and the same documentation says that starting in Microsoft Edge version 156 that policy is deprecated because the built-in PDF reader experience has transitioned to the newer version, with the policy planned to become obsolete starting version 162, and the newer reader's documented additions include higher coverage of digital signature verification, MIP sensitivity label viewing, Undo and Redo for PDF annotations on Windows, faster Read Aloud, Copilot Summarize and Explain actions, and XFA viewing through the IE mode policies; the scope is the built-in viewer rather than a separate application, does not claim editing or creating PDFs, and does not claim the legacy reader's feature set for the new engine or the reverse
Where your files are processed
Mixed - depends on version and feature
The vendor's own documentation separates them. On the device: Edge on Windows, Edge on macOS. On their servers: Viewing Purview-protected files. A single answer for the whole product would be wrong for one of them.
Architectural: a local Chromium-based browser that renders and opens PDFs on the device, with process isolation for PDFs per Microsoft's own documentation. Caveats: online and embedded PDFs are fetched from their host, and viewing Purview-protected files requires a signed-in identity and licence, at which point content handling depends on Microsoft's cloud.
What it does
Edge opens local, web-hosted and embedded PDFs in the browser, with zoom, rotate, fit-to-page, search, page views, a table-of-contents pane and read aloud. You can fill basic form fields, highlight text, attach text notes to a selection and draw ink with a mouse or stylus.
Edge can display and validate certificate-based digital signatures and open Purview-protected PDFs when signed in with sufficient permissions. Microsoft has been moving the built-in reader to a new engine powered by Adobe Acrobat since Edge 141, and from Edge 156 the policy that selects the older reader is deprecated.
Best for
People already working in Edge who need to read, fill, sign by hand and mark up PDFs without leaving the browser, including work users who must open protected files.
Worth knowing
No redaction, no compression, no format conversion, and it cannot create digital signatures - only view and validate them. JavaScript forms are not supported in the documented feature list, and XML Forms Architecture (XFA) PDFs are not supported natively: an administrator can allow them to open in IE mode through the ViewXFAPDFInIEModeAllowedOrigins or ViewXFAPDFInIEModeAllowedFileHash policies.
The reader is also mid-transition. The Adobe Acrobat-powered reader is the default from Edge 141, the NewPDFReaderEnabled policy that selects the older reader is deprecated from Edge 156 and planned to become obsolete from Edge 162, and the newer engine adds its own features, so which documented behaviours apply depends on the engine in use and on policy.
Details, and where each comes from
Vendor statements, our own reading of their pages, and the things nobody has established yet, each answered separately. Where we have not confirmed something it says so rather than guessing, and a row nobody has established is greyed out.
- Versions covered
- Web · Windows · macOS
- Website
- learn.microsoft.com
- Requires an account
- No
- Watermark on the free tier
- Not verified
- Maximum file size
- Not verified
- Batch processing
- No
- Data residency
- Self-hosted
- Open source
- No
- Self-hostable
- Not verified
- Licence
- Proprietary
- Redaction
- No redaction feature
- Programmatic access
- None
- Last availability check
- Responded in 142 ms 21 October 2026
Checked automatically by our own runner, not reported by the vendor. 100% of our last 30 checks got a response.
What the redaction verdict rests on
From the vendor's own documentation, read 22 September 2026. Not tested by us.
What that does not establish
The vendor’s own site was read on 22 September 2026 and contains no mention of redaction, sanitisation, blackout or whiteout. Absence from a vendor’s own material is not proof that a feature does not exist - it may be undocumented, or on a page the reading did not reach - but for a NEGATIVE claim it is the strongest evidence available, and it is weaker than a positive quote.
Recorded as such rather than presented as certainty.
https://learn.microsoft.com/en-ca/deployedge/microsoft-edge-pdf
What the vendor says
Claims are labelled rather than repeated as fact. Where we have checked something ourselves, it says so and shows when. Checked means we read the vendor's own page and it says what we recorded - not that we tested the behaviour, unless the note says we did.
-
“Microsoft Edge comes with a built-in PDF reader that lets you open your local pdf files, online pdf files, or pdf files embedded in web pages.”
Checked by us - the source says this Read 22 September 2026
Confirmed verbatim: the sentence opens the article's description of the built-in reader and continues by naming what it can do - annotate with ink and highlighting, and serve as "a single application to meet web page and PDF document needs". It is a capability claim from Microsoft's own deployment documentation for administrators rather than from a marketing page, which makes it the more reliable kind of source.
Note the small inconsistency the vendor leaves in: "local pdf files" is lower-cased where PDF is capitalised everywhere else on the page.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 1587fc12800ed6202344bfd067cec622d1b2bbb91a3519f8fc74f76b21b632c9
How we checked
Re-verified verbatim on 2026-09-22: https://learn.microsoft.com/en-ca/deployedge/microsoft-edge-pdf re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-learn-microsoft-com-en-ca-deployedge-microsoft-edge-pdf-7bc59bcf.txt.
-
“The Microsoft Edge PDF reader is a secure and reliable application that works across the Windows and macOS desktop platforms.”
Checked by us - the source says this Read 22 September 2026
Confirmed verbatim: the sentence closes the paragraph describing the built-in reader, and the platform scope is repeated later on the same page where keyboard accessibility, high contrast mode and screen reader support are said to work "across Windows and macOS devices". So the two-platform claim is consistent in two places rather than stated once.
"Secure and reliable" is the vendor's own characterisation and is not a checkable property; what the page does document is features, not security testing. Recorded as the vendor's description; no control was run.
Note this is Microsoft's own deployment documentation for enterprise administrators, which is a more precise source than a product marketing page.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 1587fc12800ed6202344bfd067cec622d1b2bbb91a3519f8fc74f76b21b632c9
How we checked
Re-verified verbatim on 2026-09-22: https://learn.microsoft.com/en-ca/deployedge/microsoft-edge-pdf re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-learn-microsoft-com-en-ca-deployedge-microsoft-edge-pdf-7bc59bcf.txt.
Each claim is quoted from the vendor's own pages. This section describes what we have and have not checked - it is not a judgement about anyone.
Sponsorship is distribution, not an endorsement or a promise of search rankings, AI citations, traffic, or sales. This listing is a free entry, compiled from published sources.