Arc browser goes dark December 22 as Browser Company shifts to Dia

The Browser Company will sunset Arc on December 22, moving users to Dia. Bookmarks, extensions, passwords and history transfer automatically, while AI features stay optional—creating a forced workflow transition.

What happened

The Browser Company will sunset its Arc browser on December 22, according to Engadget. The company has shifted attention to Dia, an AI browser first announced last year. Users are being steered from Arc to Dia, and the company says all bookmarks, extensions, passwords and history will transfer over automatically.

On December 22, Arc users will no longer be able to access their accounts. Engadget notes the browser offered people the ability to personalize any website while browsing, but never quite caught on. The company is also courting users who are wary of AI by emphasizing that additional AI features in Dia are optional.

Dia positions itself as a standard AI-based web browser. The company says a chatbot can understand context across multiple open tabs, summarize emails and YouTube videos, and produce a daily "morning brief" that integrates data from calendars, inboxes and web links.

Key facts

• Arc will be sunset on December 22, and users will no longer be able to access their accounts that day.
• The Browser Company is prioritizing Dia, an AI browser first announced last year.
• Bookmarks, extensions, passwords and history transfer over automatically from Arc to Dia.
• Dia includes a chatbot that can understand context across multiple open tabs, summarize emails and YouTube videos, and build a morning brief from calendars, inboxes and web links.
• Arc-to-Dia AI features are optional, which the company is using to appeal to users cautious about generative AI.

Our analysis

This is less a browser update and more a forced migration into a product that treats browsing as an AI-assisted workflow. The automatic transfer of bookmarks, extensions, passwords and history lowers friction, but it also moves users into a new interaction model. Arc let people personalize any website while browsing; Dia is built around a chatbot, tab-level context, summarization and a morning brief. That shift likely matters most to social media managers, creators and community operators who used Arc for lightweight brand monitoring, content drafting or organizing client work across tabs.

For those users, the end of Arc removes a site-level personalization layer and replaces it with an environment where the browser can read context across open tabs. The reported ability to summarize YouTube videos and emails suggests Dia is designed for research intake and briefing tasks rather than deep visual customization of individual pages. Because AI features are optional, operators can likely keep a more conventional setup initially, but the product direction points toward automating daily research and reporting.

What changes is emphasis: from changing how websites look to changing how information from websites, calendars and inboxes is assembled and summarized. The hard shutoff also creates a real deadline. After December 22, Arc accounts are inaccessible, so any saved customizations outside the listed transfer items may no longer be recoverable.

What it means for operators

• Audit your Arc setup before December 22. Confirm which bookmarks, extensions, passwords and history you expect to appear in Dia, and document anything beyond that list because site personalizations or workspaces may not carry over.
• Test the Dia migration early. The transfer is reported to be automatic, but verify that extensions are installed and that passwords and history are accessible before the Arc account lockout.
• Treat optional AI features as a workflow and privacy decision. Keep the chatbot, email summarization and YouTube summarization disabled unless your process benefits from a browser reading context across multiple open tabs.
• Update team runbooks for research and content intake. If Dia's morning brief pulls calendars, inboxes and web links, decide which accounts should be connected and make clear what is shared before rolling it out to creators or community staff.