Why Opera Switched from Presto to Chromium in 2013

In 2013, Opera Software made the monumental decision to abandon its proprietary Presto rendering engine in favor of the open-source Chromium platform. This article explores the primary catalysts behind this transition, including the rising costs of maintaining an independent engine, widespread web compatibility issues caused by the dominance of rival browsers, the need to reallocate resources toward user-facing features, and the strategic push to stay competitive in the rapidly growing mobile market.

Web Compatibility Issues

The most pressing issue for Opera was website compatibility. By 2013, Google Chrome and Apple Safari had gained massive market share, both powered by the WebKit engine. Consequently, web developers began optimizing websites specifically for WebKit, often ignoring strict web standards in the process.

Because Opera held a relatively small slice of the desktop market, developers rarely tested their sites on the Presto engine. This resulted in broken layouts and malfunctioning web applications for Opera users. Opera had to employ a team just to contact webmasters to fix their code, or write custom patches to force sites to render correctly. Moving to Chromium instantly solved this problem, as Opera could now render the web identically to Google Chrome.

The High Cost of Engine Maintenance

Modern web standards, particularly HTML5 and CSS3, were evolving at an unprecedented pace in the early 2010s. Maintaining a proprietary rendering engine required massive financial and human resources just to keep up with basic standards, security patches, and performance benchmarks.

Opera was competing against tech giants like Google, Apple, and Microsoft, who had vastly superior budgets. Building and maintaining the Presto engine from scratch was no longer financially viable when a superior, open-source alternative—Chromium—was freely available and maintained by a global community of developers.

Shifting Focus to User Innovation

Historically, Opera was known as an innovator, introducing features like tabbed browsing, speed dials, and mouse gestures long before its competitors. However, by 2013, the bulk of Opera’s engineering talent was tied up in back-end engine maintenance rather than front-end innovation.

By adopting the Chromium platform and its Blink rendering engine, Opera freed its developers from the burden of building the underlying plumbing of the browser. This allowed the company to redirect its resources toward creating unique user-facing features, refining the user interface, and differentiating the browser through built-in tools rather than how it parsed HTML.

Demands of the Mobile Market

The explosion of the smartphone market on iOS and Android changed how users accessed the internet. While Opera Mini and Opera Mobile were successful on older feature phones, the Presto engine struggled to compete with the performance and integration of native browsers on modern smartphones.

The mobile web was heavily built around WebKit. To build a fast, modern, and compatible browser for Android, Opera needed an architecture that was already optimized for the platform. Transitioning to Chromium allowed Opera to quickly deploy a high-performance mobile browser that could seamlessly handle modern mobile web applications.