Opera has been making web browsers for nearly two decades, but the Opera browser for desktop computers has never come close to rivaling Firefox, Internet Explorer, Safari, or Chrome in popularity. Opera’s mobile browsers, on the other hand, have been quite popular in recent years — Opera says it now has 300 million active users across all of its PC and mobile browsers.

So it’s an interesting time to see the company announce a major change: Over the next year Opera will be moving from its own Presto rendering engine to WebKit, an open source rendering engine used to load web pages in Safari, Chrome, and many other web browsers.

Update: Did I say Webkit? I meant Blink. Opera will be using Google’s Chromium project as the basis for its rendering engine, and since Google is forking Chromium and building its own product called Blink, that’s what Opera will use too.

Opera web browser

Presto is a speedy rendering engine, and it’s designed to support web standards — but because Opera isn’t as widely used as some other browsers, many web developers don’t bother to test their apps to see if they’re compatible. As a result, while Opera strives to support web standards as much (or more) than any other company, there are still some popular web sites and web apps that don’t load properly.

By moving to WebKit, Opera can spend more time adding features to its browsers rather than working to improve the underlying rendering engine.

The developers are already contributing to the development of WebKit and Google’s Chromium open source browser, so the company isn’t giving up on development of rendering engines altogether. But by adopting an existing engine the company can free up many developers to work on other aspects of its software.

So what does this mean for users going forward? While upcoming versions of Opera will likely maintain existing features such as Speed Dial (shortcuts to your favorite websites on the new tab page) and Link (which lets you sync your data across device), developers at Opera are also working on entirely new ways to interact with a browser.

For instance, last month the company showed off an upcoming gesture-based web browser based on WebKit. It’s code-named ICE, and it’s designed for tablets and other mobile devices. Opera also plans to show off a new Opera browser for Android at Mobile World Congress later this month.

Support Liliputing

Liliputing's primary sources of revenue are advertising and affiliate links (if you click the "Shop" button at the top of the page and buy something on Amazon, for example, we'll get a small commission).

But there are several ways you can support the site directly even if you're using an ad blocker* and hate online shopping.

Contribute to our Patreon campaign


Contribute via PayPal

* If you are using an ad blocker like uBlock Origin and seeing a pop-up message at the bottom of the screen, we have a guide that may help you disable it.

Subscribe to Liliputing via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 9,542 other subscribers

3 replies on “Opera moves to Webkit for PC, mobile web browsers”

  1. For what its worth, Opera Mini is a transformative piece of software for higher end feature phones (like the Nokia Asha line.) I hope this announcement signals even more priorities being dedicated to these niches in which they are dominant.

  2. This is great news. After having been partial to Opera for a decade, I switched to Chrome about six months ago because a few websites I need for my job don’t play well with Opera. There are certain things — MRU tab order, tab grouping, and gestures are some obvious ones — that Opera originated and has always done right. I often find myself cussing Chrome for getting these features wrong. Maybe sometime in the next year I’ll be able to switch back to Opera, and life (or web browsing at least) will be good again.

  3. Actually I was pretty surprised to hear such, as mobile Opera performs WAY better than mobile Chrome on every Android device I’ve tested. I’m mainly focusing on the canvas element too.

Comments are closed.