A browser maker paused Arc's features to build something else

What the letter actually states

In a letter to Arc members published 26 May 2025, The Browser Company confirmed what many users had already noticed: it was not actively developing the core product experience like it used to. The company said it would continue Chromium version upgrades and security fixes, keeping Arc functional and current on the underlying browser engine, but stopped short of promising new features. In the same letter, the company set out where its effort was going instead: Dia, a browser it describes as built around AI from the ground up, with the stated belief that traditional browsers, as known today, will die as interfaces are reshaped around AI assistance.

What paused looks like in practice

Arc's own current website makes the practical consequence explicit to anyone downloading it today: a notice states that Arc receives Chromium updates only, and that active security patches and enterprise-grade protection require downloading Dia instead. That is a narrower promise than ordinary maintenance. Chromium updates keep the browser's rendering engine current, which matters for compatibility with modern websites, but the company's own wording draws a line between that baseline and the fuller security and feature attention it says now goes to Dia. Arc, in other words, is being kept running rather than being developed, a distinction the company states rather than one a user has to infer.

What to weigh when a tool's future is announced this way

A devoted user base built habits and workflows, like Spaces and Split View, around Arc's specific design choices. The company's letter frames its pivot as continuity of vision rather than abandonment, arguing Dia pursues the company's original vision through new means. That framing may be sincere, but it does not change the operational fact for a current Arc user: a browser that has stopped receiving new features is a browser whose long-term roadmap now depends entirely on a different, separately released product succeeding. The letter also states an intention to open access for Arc members next, meaning migration to Dia was, at the time of writing, still being staged rather than completed for existing Arc users.

Questions to ask before you adopt it

• Is the tool you are considering still receiving full security support, or only a narrower maintenance tier like Chromium updates?
• Has the maker stated where its product effort is actually going, in its own words, rather than leaving you to infer it from an absence of updates?
• What would it cost you to move saved tabs, spaces, or workflows to a replacement if the current tool is later retired outright?

The company's letter is a primary, dated statement of intent, and it is unusually direct about what has already changed. It does not resolve whether Dia will replace Arc's role for its existing users, only that Arc's own maker no longer treats new development as the browser's future.