Arc Browser (2026): The Browser Company's Frozen Favourite Under Atlassian

Arc is in an unusual position for a product review: it is neither dead nor alive in any meaningful product-roadmap sense. Development stopped on 27 May 2025, Atlassian bought The Browser Company for $610 million in a deal that closed on 21 October 2025, and the engineering team moved on to Dia, an AI-first browser. Arc got a single passing mention in the acquisition announcement, which tells you most of what you need to know about its priority.

What makes this more than a eulogy is that the software genuinely still functions. Mac and Windows builds shipped in June 2026 on a current Chromium release, Arc Search on Android is still being updated, downloads are still live, Chrome extensions still work and sync was reported healthy as recently as May 2026. In other words, Arc is being kept structurally sound rather than left to rot — the lights are on, nobody is redecorating.

This is for one group above all: existing Arc users who love the sidebar, Spaces and the Cmd+T command bar and are trying to decide whether to panic. It is a much harder sell to anyone starting fresh, who would be adopting a workflow nobody is going to extend.

Judged purely as a browser you can open tomorrow morning, Arc holds up. The security story is the reassuring part: Chromium engine patches are still landing on both desktop platforms, and the two most recent macOS and Windows releases arrived less than a month apart, on the same Chromium version. The risk here is stagnation, not exposure — an important distinction that gets lost in the "Arc is dead" headlines.

The problems are all forward-looking. Only critical bugs get fixed, so any annoyance you hit today is an annoyance you keep. Feature requests go nowhere. There is no published end-of-life date, which sounds like good news but is actually the worst kind of uncertainty: you cannot plan a migration around a deadline that does not exist, and a new owner with a competing AI-first browser in public beta has every incentive to eventually set one. Anyone building team habits or workflows on Arc is building on a platform with a silent countdown.

The mitigating factor is that the thing people actually miss about Arc is its interface philosophy, not its rendering engine — and much of that sidebar-and-Spaces workflow is reproducible in Chrome or with third-party tools. That makes the eventual exit less traumatic than it first appears, but it also undercuts the case for staying.

A fair rating has to split the difference between a genuinely good browser and a genuinely terminal product strategy. Keep using it if you already love it, keep a migration plan in your back pocket, and do not start new projects on it. One honest caveat on our confidence: we are assessing status and support here, and some details around Dia's launch timing and Arc's original release date are less firmly established than the maintenance-mode and acquisition facts.