What Browser Engine Did ChatGPT Atlas Use?
OpenAI’s discontinued Mac browser ran on familiar Chromium technology, but its unusual OWL architecture separated the web engine from the app. Here’s how it worked and why it matters.
Atlas used Chromium’s Blink engine, not a new AI renderer.
ChatGPT Atlas used Blink to render websites and V8 to run JavaScript. Both technologies came from the open-source Chromium project, which also underpins Google Chrome and several other browsers. OpenAI did not create a separate rendering engine for Atlas.
Instead, it developed an original Mac interface and a layer called OWL (OpenAI’s Web Layer) to connect that interface to Chromium. Atlas launched for macOS on 21 October 2025 and was retired in 2026. OpenAI now confirms that the browser no longer receives updates.
Turned web page code into visible content.
Executed JavaScript and WebAssembly in Chromium.
Linked Chromium’s processes with the native Mac app.
The unusual part was OWL, not Blink.
OpenAI put the user-facing macOS application and Chromium’s browser runtime into distinct processes, communicating through a purpose-built integration layer.
Browser interface built using SwiftUI and AppKit, with Metal for graphics work.
Site navigation, page content, rendering and browser services.
The native app handled the browser chrome, tabs and the ChatGPT experience.
OWL used Chromium’s Mojo messaging system to communicate between processes.
Chromium handled webpages using Blink, with V8 running their scripts.
OpenAI described the native app as the OWL Client and the Chromium process as the OWL Host. Its engineering account says this arrangement let Chromium start asynchronously, helped isolate interface responsiveness from Chromium stalls, and reduced the amount of Chromium user-interface code OpenAI had to maintain.
That separation also mattered for AI browsing. Atlas could request actions in web content while the architecture routed agent-generated events to the renderer rather than granting those events direct control over privileged browser actions. These were design safeguards, not proof that AI-driven browsing carried no risk.
An AI assistant therefore did not replace the browser engine. The assistant interpreted pages and handled tasks, while a standard web-rendering stack still displayed and executed the underlying websites. Our guide to AI agent traffic explains the separate network activity that automated visits can generate.
From October 2025 launch to August 2026 shutdown
Atlas had a short life as a standalone browser. These are the dates that can be supported by OpenAI’s own records.
OpenAI introduces a Chromium-based browser with ChatGPT alongside the web page, plus an agent mode for supported tasks.
OpenAI publishes technical details of its native Mac application, separate Chromium host and Mojo-based integration.
OpenAI announces its plan to wind down Atlas and move browser-based agentic capabilities into ChatGPT and Codex.
OpenAI identifies this as the date Atlas was scheduled to stop working, with users asked to preserve browser data beforehand.
OpenAI’s retirement guidance says Atlas has been retired and no longer receives updates. This is a verification date, not a separate launch event.
Why the dates matter: “Launched in 2025” describes when Atlas became available; “retired in 2026” describes its present status. A comparison written in the present tense would mislead readers now.
Was Atlas just Google Chrome with a chatbot?
It shared Chrome’s central rendering technology, but its native interface and Chromium integration were different.
Uses Blink to render sites and V8 for JavaScript, with Google’s own browser interface and services. Chrome’s core interface follows Chromium’s browser architecture more closely.
Used the same Blink/V8 foundations, but connected a SwiftUI/AppKit browser application to Chromium through OWL. ChatGPT and agent tasks were integrated into that application.
The common engine meant sites were largely relying on the same web standards implementation, although behaviour could still differ due to Chromium version, permissions, features or the surrounding browser application. The fact that Atlas used Blink did not make it an official Chrome edition.
It also was not a Safari or Firefox derivative. Atlas was released as a macOS app; OpenAI did not announce generally available Windows, Android or iOS editions before retiring it. Unlike some other browsers in this series, there was no shipped iPhone edition requiring a second engine comparison.
For wider context on how we reached this concentration of rendering engines, read our history of the internet and the rise of browsers.
What replaced Atlas, and what happened to its data?
OpenAI moved its browser-based agentic work into ChatGPT and Codex rather than keeping Atlas as a separately maintained browser.
Bookmarks, open tabs and browsing history were separate from ChatGPT conversations. Previously exported bookmarks can be imported into another browser.
Saved password files can contain readable secrets. Cookies and session files should not be shared. Sign in again where required.
OpenAI points users towards supported ChatGPT desktop, browser extension and other browser-based experiences where available.
OpenAI’s current retirement guidance states that users without a previous Atlas data export may have to contact support, and that recovery cannot be guaranteed. ChatGPT conversations remained separate from Atlas’s local browser data and were not automatically lost because the browser retired.
It would be inaccurate to say the new ChatGPT browser features are simply Atlas under another name, or to assume they use exactly the same architecture. OpenAI says it is building on what it learned from Atlas, but has not presented every successor experience as the same standalone product.
One broader question raised by Atlas is how much work an AI agent can do on the live web. Our dedicated guide to AI-generated internet traffic covers those requests and their network impact, without confusing them with web rendering.
Blink powered the pages. OWL made Atlas different.
Atlas did not invent a new browser engine: it used Chromium’s Blink and V8. Its distinctive engineering was the Mac-native app and OWL bridge around them. Because Atlas is retired, the useful lesson now is architectural, not a reason to install an unsupported browser.
ChatGPT Atlas engine FAQs
Did ChatGPT Atlas use Chromium or WebKit?
Atlas used Chromium, including its Blink rendering engine and V8 JavaScript engine. OpenAI’s OWL layer connected Chromium to Atlas’s native macOS application. It was not built on Safari’s WebKit engine.
Was OWL a replacement for Blink?
No. OWL stood for OpenAI’s Web Layer. It connected Atlas’s application to a separate Chromium browser process; Blink still rendered websites and V8 executed JavaScript.
When did ChatGPT Atlas shut down?
OpenAI scheduled Atlas to stop working on 9 August 2026. By October 2026, its retirement page confirmed the product had been retired and no longer received updates.
Can I still recover bookmarks or passwords from Atlas?
If you exported them previously, you can import compatible bookmarks or passwords into a supported browser. Atlas data did not migrate automatically, and OpenAI says recovery without an existing export is not guaranteed. Treat any exported password file as sensitive.
