Microsoft has delayed a key update for its Edge browser, postponing the adoption of Adobe’s PDF engine. This shift in the schedule is unexpected, as the original timeline had the migration commencing by March 2023 with an estimated completion in early 2024. The new timeline now extends the wait for Edge users, as the integration isn’t expected to begin until early 2025 at the earliest. The delay represents a significant deviation from the plan that was anticipated by users and tech industry observers alike. This extension might affect how consumers and organizations utilize Edge for PDF-related tasks. Microsoft has yet to provide detailed reasons for the postponement or discuss the potential implications of this delayed implementation for the browser’s functionality and user experience. The prolonged timeline could alter the competitive landscape for browser-based PDF tools, and users invested in the Edge ecosystem may need to adjust their expectations and workflows accordingly.
Revised Migration Timeline
The postponement was divulged through an update on Microsoft’s Tech Community website, leaving the tech community to wonder about the reasons behind this delay. Microsoft Edge, currently equipped with its own PDF engine, was expected to see a major shift to Adobe’s PDF technology, promising a unique browsing experience with improved fidelity, performance, security, and accessibility. It was also hinted that despite the base viewing and editing features being free, Edge users could get access to advanced functionalities through an Acrobat subscription.
The update strives to inform that the changeover to Adobe PDF technology in Edge for consumer-grade devices has been rescheduled to the middle of the summer, with no explicit year mentioned but inferred to be 2024. This delay also implies that the current Microsoft Edge PDF engine will remain functional in the browser at least until early 2025. Interestingly, while the deployment for home users is being delayed, managed devices could potentially be switched over to the new PDF engine manually, allowing a subset of users to experience Adobe’s PDF technology beforehand.
Speculations and Workarounds
Tech observers suggest that Adobe’s difficulty in managing XFA forms may be behind Microsoft Edge’s delayed incorporation of Adobe’s PDF engine. Though Adobe Reader and Acrobat can handle these forms, Microsoft hasn’t disclosed the reasons for the holdup, fueling speculation. Users keen on experiencing Adobe’s PDF features in Edge can access them by enabling the New PDF Viewer in the browser’s experimental settings, as indicated by the “powered by Adobe Acrobat” label upon opening a PDF. While this offers advanced functionalities, there’s an unavoidable “edit with Acrobat” button linked to Adobe’s paid services. This situation leaves some users in a quandary—frustrated by the waiting yet potentially appreciative of the continued access to the current Edge PDF reader during this interim period.