Arc Browser is shutting down on December 22, 2026. The Browser Company says maintaining browser security requires sustained engineering work, and it will concentrate its engineering and security teams on Dia. This is an announced end of service, beyond the earlier decision to stop developing new Arc features. The official farewell page gives the dates and platform-specific consequences.
For people who built a working day around Arc, an importer answers only part of the problem. In the announcement discussion, Reddit user danroesser objected to the disruption of a “professional workflow” and said they would have paid for Arc. That is one person's response, but it identifies the practical question: which parts of your way of working will survive the move?
Below is an explanation of the decision, what the official statements establish, and a migration plan. Tabbit Browser is one option to evaluate if you want vertical tab organization alongside AI that can work with your pages and files. That evaluation should start with a real project and an export you can keep.
Key takeaways
Arc on macOS and Windows will stop working on December 22, 2026. Plan around the published deadline.
The immediate explanation is security maintenance and concentrating staff on Dia. The longer product history includes adoption difficulties and architecture choices.
The company presents Dia as the replacement, with free browser features and optional AI. Its current announcement includes Windows, so older Mac-only comparisons need checking.
Arc Search has a separate mobile schedule. iOS retains a lite browser; Android reaches full deprecation in December.
Preserve your links first, then test your daily workflow in a replacement. Tabbit is a candidate for browser-based research and AI work, with migration details to verify.
Arc's shutdown timeline at a glance
| Date | What the official page says | What to do |
|---|---|---|
| October 22, 2026 | New Arc accounts end; existing members can continue; the latest version includes export options | Update and save an export while you can still access your setup |
| November 23, 2026 | Arc Search on iOS and Android loses Browse for Me, other AI features, sign-in and tab sync | Export mobile tabs and choose a replacement for those functions |
| December 22, 2026 | Arc on macOS and Windows stops working; Arc accounts are deactivated; Android Arc Search is fully deprecated | Finish desktop migration before this date; iOS keeps a lite browser |
| Within 30 days of account deactivation | Personal data associated with Arc accounts is deleted | Keep your own verified copy; this is not an additional recovery window |
Source: Arc's current timeline and FAQ, checked October 23, 2026. The company also says that from December 22 it cannot identify or retrieve Arc user data for data requests. The 30-day deletion period should not be treated as permission to postpone exporting.
The X announcement may display October 23 in an Asian time zone. The official website dates the start of the shutdown process October 22. Both refer to the same announcement; neither changes the December deadline.
Why is Arc shutting down?
The immediate decision is to concentrate security work on Dia
In the announcement supplied for this article, the company explains that security requires constant dedicated work, with that demand increasing as AI becomes part of browsing. It says Dia was built for current security standards and is where its engineering and security teams will focus.
That establishes a decision about staffing and product priorities. It does not establish that every existing Arc installation has been compromised, or that a particular newly discovered vulnerability caused the shutdown. The announcement identifies no such triggering incident. Treating “security” as evidence of an undisclosed breach would go beyond the source.
The practical distinction matters. A browser that can open a page today still needs an organization prepared to maintain it tomorrow. Staying with Arc until the deadline is a temporary transition plan. Assuming it will remain a supported daily browser afterward contradicts the official notice.
Arc's enthusiastic audience did not match the company's intended scale
The shutdown follows a much earlier product decision. In its May 27, 2025 letter to Arc members, The Browser Company described a gap between the committed audience it had earned and the broad adoption it wanted. Too many changes to familiar browsing behavior made the initial learning effort difficult to justify for many newcomers.
The letter's figures are useful when read narrowly. It said 5.52% of daily active users regularly used more than one Space, 4.17% used Live Folders, and 0.4% used Calendar Preview on Hover. These are company-reported figures from 2025, without a public dataset for this article to reproduce. They measure specific behaviors, not whether 95% of users disliked Arc. In particular, using one Space consistently can be entirely useful.
The analysis is that Arc could be valuable to a specialist audience while missing its maker's mass-market ambition. A person who appreciates a polished sidebar and a repeatable routine can reasonably regard Arc as successful. A company seeking a much wider behavioral change can reach a different conclusion about the same product. Neither judgment cancels the other.
This also explains why “just make it paid” does not settle the issue. Some users express willingness to pay. That is evidence of demand from those users, not an audited revenue model or proof the company wanted to operate a smaller paid product. There is no basis here to label the shutdown a bankruptcy.
Building Dia separately was an architectural and strategic choice
The 2025 letter also described performance and architecture constraints behind the decision to build a separate browser. Those are the company's explanation of its own engineering choices. They are not independent measurements establishing that every Dia task is faster than the equivalent Arc task.
The current farewell page now says Dia exceeds Arc on stability, speed and security. No reproducible benchmark methodology accompanies that statement on the page. A migration decision should therefore test the activities that matter to you: opening a large project, finding a pinned page, authenticating to work tools, and using essential extensions. Our Dia and Arc comparison is a starting point for those questions; the latest official notice takes precedence over older availability information.
There is also a clear direction in Atlassian's September 2025 acquisition announcement: its stated ambition centers on Dia and knowledge work. That supports the observation that investment is going toward Dia. It does not prove that Atlassian ordered Arc's shutdown, or that the acquisition alone caused it. The Arc-to-Dia pivot was already public months earlier.
Why importing the data does not settle the workflow question
The current official migration offer is substantial. The company says Dia can import passwords, bookmarks, extensions, history, tabs and other supported setup data on macOS and Windows. Spaces become Profiles; Folders become Tab Groups. It also lists Sidebar tabs, Pinned Tabs and Split View among the familiar features. Browser features are free, and AI is optional, according to the notice.
It would be inaccurate to dismiss Dia as a paid AI requirement or a Mac-only option on the basis of older articles. It would also be inaccurate to assume that a list of supported imports guarantees an identical experience.
For example, designer Andreas Storm responded by asking Dia to add Peek as an option. Another user, Drin, raised concerns about their Windows experience and sync. These are specific user priorities at the time of the announcement. They do not establish a universal missing-feature list or a verified current defect.
The useful test is whether you can complete your routine without rebuilding it every morning. Write down the five actions you repeat most. Include context switching, previews, keyboard commands, extension behavior and reopening yesterday's project. Use that list when evaluating browsers with Arc-like workspaces, rather than picking a replacement from a screenshot alone.
A practical option for research and AI work: Tabbit Browser
If Arc's appeal was keeping a research project visible while you worked, Tabbit is worth testing. Its current international website describes referencing pages, screenshots, highlighted text and local files as AI context. The Chinese website also demonstrates vertical tab organization and grouping. Available platforms, models and plans must be checked for the edition you install.
Consider a project with several product documents and a local requirements file. Open copies of the source pages, organize them into a manageable group, and reference the relevant pages and file in a conversation. Ask for a comparison with source links and unresolved questions. The intended result is a reviewable working note you can save outside the browser. This is a proposed workflow based on official capabilities, not a claim that the author ran a timed comparison.
Compare the referenced product pages against the attached requirements.
For each requirement, list supporting evidence, its source URL,
and anything the sources do not establish. Do not infer missing facts.
Finish with the questions I need to verify manually.The Tabbit introduction explains the context and task model. AI tab organization addresses grouping; if the problem is simply an overloaded window, the tab cleanup guide may already be enough. AI-generated comparisons and groups still need checking. Model requests can involve sending the context you select to a provider, so choose appropriate material and check the relevant privacy settings.
The migration boundary is important: this research did not verify a direct Arc importer in Tabbit or preservation of Arc Spaces, Peek and every shortcut. Export Arc's links, reopen one project in Tabbit and rebuild the structure deliberately. Treat it as a second-browser trial until your actual routine works.
Export before choosing your next default browser
The official export instructions now identify specific controls:
On macOS, open Arc → Settings → Advanced → Export Data.
On Windows, open Settings with Ctrl+,, then find Export Spaces and tabs → Export Data in Advanced.
Save the file somewhere you control. Open it and check that important URLs and the project structure you need are represented.
Export mobile tabs separately through Arc Search's settings. Do this before mobile sign-in and sync end.
In the replacement, reopen a small project and check logins, essential extensions, shortcuts, downloads and an independent way to save your work.
The official third-party export is described as a list of links. Do not assume it contains passwords, authenticated sessions or unsaved form content. Handle those separately. Dia's supported direct import is a different path and does not prove other browsers have the same importer.
If your project currently lives only in open tabs, create a durable bookmark or project document too. A browser session manager can help preserve a working set, but it does not remove the need to verify the copy before Arc closes. The aim is to make the project recoverable when the application changes.
Choose by the work you need to preserve
| Your priority | First option to evaluate | Pass condition |
|---|---|---|
| Bring across the most Arc-specific setup through the official route | Dia's Arc import | Check Profiles, groups, pins, passwords and your daily shortcuts |
| Keep a project visible and use pages and files with AI | Tabbit | Complete one real project; check the edition's features and export the result |
| Preserve a particular Arc interaction | Compare alternatives around that interaction | Test the exact preview, shortcut or context switch before committing |
| Keep an employer-approved environment | Your organization's approved browser | Confirm authentication, required extensions and device policy |
| Keep access to old research regardless of the next browser | Arc export plus an independent project record | Reopen the important URLs outside Arc before the deadline |
For a broader shortlist, use the Arc alternatives guide alongside the current official status of each product. Organization and AI assistance are separate requirements. A replacement earns the role when it supports the work you actually repeat.
Arc closes because its maker is concentrating maintenance and product investment on Dia, after concluding that Arc's design and architecture did not serve the scale it wanted. That is the defensible reading of the public record. The lesson for users is practical: keep your work portable, test the next browser with a real project, and finish before December 22. If that project depends on gathering and comparing information across pages and files, try Tabbit with a copy of it and use the download below to begin that trial.
FAQ
When is Arc Browser shutting down?
Arc for macOS and Windows will stop working on December 22, 2026, according to the official farewell page. New accounts stopped on October 22. Export your important data before the December deadline.
Why is Arc closing if people still love it?
The company says security maintenance requires continuous dedicated work and its engineering and security teams will focus on Dia. Its earlier explanation also described adoption difficulties and architectural limitations. A loyal audience and the company's growth ambitions are different measures of success.
Can I keep using Arc offline after December 22?
The company explicitly says the desktop app will stop working. It has not promised a supported offline mode that bypasses the shutdown. Do not make continued access to your working tabs depend on that possibility.
What happens to Arc Search on iPhone and Android?
AI features, sign-in and tab sync end on November 23, 2026, on both platforms. A lite browser remains on iOS. Arc Search for Android is fully deprecated on December 22 and removed from Google Play, according to the official notice.
Will Arc Spaces transfer to Dia or Tabbit?
The company says Dia imports Arc Spaces as Profiles and Folders as Tab Groups, along with other supported data. A direct transfer preserving Arc Spaces in Tabbit has not been verified for this article. For another browser, export the official list of links and rebuild and check the structure you need.
Is Tabbit a suitable Arc alternative?
Tabbit is worth evaluating if your work combines vertical tabs, page and file context, and AI assistance. It is not a verified feature-for-feature Arc replacement, and this article does not claim a direct Arc importer. Test one project, essential extensions and export options before changing your default browser.