/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Microsoft plans to embed Adobe's Acrobat PDF tech in Edge for Windows 10 and Windows 11 starting in March 2023 and remove Edge's legacy PDF engine in March 2024

Thurrott Paul Thurrott

Context & Ripple Effects

Edge's handling of PDFs has been a quiet feature battleground since Microsoft rebuilt the browser on Chromium — the October 2020 update that added improved PDF support alongside price comparison and screenshots was part of that push. Embedding Adobe's Acrobat technology is a different move: rather than improving its own engine, Microsoft is licensing the category leader's stack outright.

The plan follows the template of the automatic Chromium-based Edge rollout to Windows 10 machines, where Microsoft swapped out a legacy component wholesale once the replacement was ready — here with a March 2023 embed and a March 2024 removal date for the old engine.

First-order effects

  • Adobe gains default-scale distribution: Acrobat's PDF technology ships inside Edge on every Windows 10 and Windows 11 machine that updates, no separate install required.
  • Microsoft retires maintenance of its own PDF rendering path, giving Edge users Acrobat-powered viewing and annotation while freeing Edge engineers from that codebase.

Second-order effects

  • Independent PDF-tool vendors that competed against Edge's built-in reader now face an Acrobat-grade native experience in the default Windows browser, squeezing the low end of their market.
  • Enterprises standardizing on Edge inherit Adobe's PDF feature set through browser updates, reducing demand for separate per-seat PDF viewers in managed fleets.

Third-order effects

The trend: Microsoft is steadily replacing homegrown Edge components with licensed or Chrome-aligned equivalents, turning the browser into a curated bundle of third-party technology.

Discussion

  • @stevesi Steven Sinofsky on x
    2/ Here's the story of what it took to get PDF into Office :-) It was a *huge* debate to do what everyone wanted and expected. https://hardcoresoftware.learningbyship ping.com/ ...
  • @stevesi Steven Sinofsky on x
    Microsoft is Bringing Adobe Acrobat PDF to Edge https://www.thurrott.com/... // Finally! 1/2