Arc Browser Shutdown: Dates, Data, and Dia Migration
Arc shuts down on December 22, 2026. Get the key dates, understand what happens to your data, compare Dia’s features, and prepare your browser migration now.
Arc Is Shutting Down: What Users Need to Know Before Moving to Dia
Arc's shutdown is no longer something you can comfortably plan around. The Browser Company says its desktop browser will stop working on December 22, 2026, and it's pointing users to Dia, its AI-first browser instead. This isn't just a rebrand: Arc accounts, syncing, mobile AI features, and access to personal data each have their own cutoff dates.
So yes, this is a migration you need to manage - not a casual "try the new browser" suggestion. If you use Arc for work, research, or a specific tab-and-profile setup, waiting until the final week is a bad bet. You'll want to understand what carries over into Dia, what changes, and what you should verify before your Arc access is deactivated.
The company says passwords, bookmarks, extensions, and history can transfer to Dia, and that Arc's features will remain free there (with AI optional). But a feature map isn't the same thing as a drop-in replacement for every workflow. This guide breaks down the shutdown dates, what to realistically expect from the move, and a checklist you can run before deadlines hit.
Arc Shutdown Dates and What Changes
The shutdown happens in phases. The tricky part is that different features stop at different times - so treat mobile Arc Search, desktop Arc, and Arc's AI features as separate items to check, not one single end date.
| Date | Change | What it means for you |
|---|---|---|
| October 22, 2026 | New Arc accounts can no longer be created | Existing users can keep using Arc during the transition, but you won't be able to sign up after this date. |
| November 23, 2026 | Arc Search loses its AI features | Features including Browse for Me are removed. Sign-in and tab syncing stop; the app continues as a basic local browser. |
| December 22, 2026 | Arc stops working on Mac and Windows | Accounts are deactivated. Personal data is scheduled to be deleted within 30 days. |
| December 22, 2026 | Arc Search is removed from Google Play | Android users shouldn't count on being able to install the app from the store after this date. |
What happens to Arc on desktop
For desktop users, the key date is December 22. On that day, Arc stops working on Mac and Windows, and Arc accounts are deactivated. The company says personal data will be deleted within 30 days.
What that means in practice: don't assume you'll be able to "figure it out later" after the cutoff. If anything matters - bookmarks, passwords, or work-specific setup - move it now and confirm it works where you're moving it.
Also, the shutdown announcement doesn't mean every local file or browser artifact on your machine will automatically disappear. But you shouldn't rely on an installed Arc copy as a long-term archive, or expect Arc's account-based functions to keep working. The safe approach is to transfer what you need and then verify the destination has it.
What changes on mobile
Arc Search changes earlier on November 23. Its AI features (including Browse for Me) will be disabled. You'll also lose sign-in and tab syncing. The app is expected to keep functioning as a basic local browser, but that's a narrower role than a synced, cross-device experience.
For Android users, there's a second issue: Arc Search will be removed from the Google Play Store on December 22. The company didn't describe the same store removal detail for iOS, so iPhone users should check the latest guidance rather than assuming the timelines match. Either way, don't confuse "still installed" with "still supported" or "still syncing."
If you want one simple rule: plan for the earliest date that affects a feature you actually use. If you rely on mobile AI or synced tabs, November 23 - not December 22 - is your deadline.
How Dia Compares With Arc
The Browser Company is positioning Dia as the place Arc users should end up - not as a totally separate product that asks you to abandon everything you already know. Some familiar pieces have direct equivalents, but the names and the day-to-day experience aren't always identical.
| Arc feature | Dia equivalent or status | Practical consideration |
|---|---|---|
| Spaces | Profiles | Separate work and personal environments still exist, just under a new name. |
| Vertical tabs | Optional sidebar layout | You can keep a vertical tab layout if it's part of your workflow. |
| Folders | Pinned Tab Groups | Saved tab organization is carried over with a different label. |
| Passwords, bookmarks, extensions, and history | Transfer to Dia | After moving, check the imported data and confirm sign-ins. |
| Arc AI features | Dia's AI capabilities; AI is optional | The company says Arc features remain free in Dia, with AI optional. |
What appears to carry over
The migration announcement specifically calls out passwords, bookmarks, extensions, and browsing history as transferable. For most people, those are the parts that make a browser feel usable immediately. Reinstalling a browser is easy; rebuilding a bookmark collection, reconfiguring extensions, and reestablishing work contexts takes time.
Dia also keeps recognizable parts of Arc's organization model. Profiles replace Spaces, and the sidebar can provide an optional vertical tab layout. Folders become Pinned Tab Groups. If your workflow relies on keeping work and personal browsing separate (or keeping tab groups organized), these equivalents should reduce the disruption.
But "equivalent" doesn't mean "identical." The name, placement, defaults, and even the feel of switching contexts can change. If your workflow depends on it, don't guess - test in Dia before the deadline. Create the profiles you use, run through your usual tab routine, and confirm your extensions and saved items are where you expect them.
AI is part of Dia's direction, not a requirement
Dia is described as AI-first, but the company also says AI is optional and Arc features will remain free. That matters. Moving to Dia doesn't necessarily mean you have to build your routine around AI or treat it like the price of keeping familiar browser features.
At the same time, Dia's overall direction is different from Arc's. Arc was known for a design-forward interface and a distinctive approach to tabs and browsing contexts. Dia is the company's current focus, and its AI positioning is central to the product. If you're deciding whether to move, look at both the practical feature set and where the company is investing.
In other words: you may be able to preserve your current habits while the product changes over time as the company prioritizes new capabilities.
The company also claims Dia surpasses Arc in speed, stability, and security. That's their assessment, not a guarantee about your specific device, extensions, or workload. Test Dia with your day-to-day use instead of treating benchmark claims as certainty.
Why Arc Is Ending - and What Its Shutdown Signals
The Browser Company says it's dealing with the rising cost of keeping a browser secure. Their explanation is straightforward: security work never stops, and they claim it's getting more demanding in the age of AI. They say Dia was built to meet current security standards, and that engineering and security resources will be focused there.
This is more than an interface design choice. A browser sits between you and a huge chunk of the web, so maintaining it means continually addressing security issues and keeping the software dependable as the environment shifts. If the company supports two browser products built on overlapping foundations, it can spread engineering attention. Their decision is to concentrate that work on Dia.
The cost of maintaining a second product
Arc's shutdown follows an earlier retreat from active feature development. In 2025, the company said Arc's novel interface and complexity limited mainstream adoption, even though early adopters were enthusiastic. They described that complexity as a "novelty tax": the product offered a different way to browse, but it required people to learn and adapt.
That trade-off is common in software. A product can be genuinely loved by a devoted group and still struggle to become a broad replacement for a standard default. Enthusiasts often accept unfamiliar patterns because the benefits matter to them. A much larger audience usually expects a browser to feel familiar with minimal setup. Cutting friction can grow the audience - but it may also mean changing what made the original product feel distinct.
Arc seems to have run into that gap. It was clearly valued by its community, but it didn't become the mass-market alternative its makers once hoped for. The shutdown is a reminder that differentiation and adoption are separate problems. You can design something thoughtfully and still not reach the scale needed to justify ongoing investment in a parallel product.
Why Arc is not being open-sourced
Some users have asked for open-sourcing. CEO Josh Miller said the blocker is Arc's connection to the Arc Development Kit (ADK). Miller has said ADK is a proprietary internal software development kit and the core engine powering Dia. Meaningfully open-sourcing Arc would also require open-sourcing ADK, which he says remains central to the company's value.
This isn't a simple "yes or no" publishing question. If a product depends on a shared proprietary engine, releasing it can expose that engine too. The company has said it would like to open-source Arc someday, but not without opening ADK. That statement doesn't promise a timeline, so for now, the best move is to plan around the announced shutdown rather than treating open-sourcing as a fallback.
The Browser Company was acquired by Atlassian for $610 million in 2025, according to the source report. The acquisition and the decision to focus engineering on Dia put Arc's end into a bigger business context: a beloved product isn't automatically sustainable if the company's resources and strategy are shifting elsewhere.
How to Prepare for the Move to Dia
A browser migration is easy to underestimate because the browser itself is free and installs quickly. The work is in the details that build up over time: saved credentials, extensions, bookmarks, browser history, and personal work patterns. A good migration isn't just clicking an import button - it's making sure the new setup is ready before the old one becomes unusable.
Use a staged migration checklist
- Identify what you rely on. Write down the Arc features and data you use regularly: profiles, tab groups, saved passwords, bookmarks, extensions, and history. Decide what's essential versus what you can rebuild.
- Check Dia's current migration instructions. The company says the listed data can transfer. Follow its latest steps, since migration options and interface behavior may change before the shutdown date.
- Move early enough to test. Don't start on December 21 as your "first attempt." Import your data while Arc is still available, then use Dia for real work and note anything that's missing or behaves differently.
- Verify the important data. Confirm key bookmarks exist, passwords are available where you expect them, extensions are installed, and your browsing contexts show up correctly through Profiles and Pinned Tab Groups.
- Review sensitive information and account access. Make sure you can still sign into the services you depend on. Also be clear on where your passwords and browser data live, and follow the browser's guidance for handling them.
- Make a fallback plan. If Dia doesn't fit your workflow, pick another browser now and figure out how you'll export or recreate what you need. Don't assume Arc will still be a usable backup after December 22.
Test workflows, not just feature labels
It's helpful to check off features, but it won't catch every problem. If you use Arc differently for work and personal browsing, test a real day: open the right profile, use your tab groups, rely on your key extensions, and sign into the services you need. If you use vertical tabs, confirm the Dia sidebar actually works for you - not just that it looks similar.
Also pay close attention to mobile. If Arc Search is part of your phone routine, test an alternative before November 23 if you depend on AI features or synced tabs. The app may continue as a local browser, but losing sign-in and syncing changes how useful it is across devices.
Do not treat migration as a backup
Importing into a new browser isn't the same as having a separate backup. If a bookmark, password, or history item is critical, make sure you understand how it's stored and whether you have another recovery route. The source announcement doesn't spell out every export detail or guarantee a perfect transfer for every setup. Check the company's documentation and keep any records you're allowed to save in a form you can actually use later.
And no, this isn't a reason to panic or copy everything everywhere. It is a reason to avoid a last-minute, all-or-nothing migration. Move what you need, verify it in Dia, and keep a fallback ready for anything that would cause a real operational problem if it went missing.
Conclusion
Arc's shutdown is happening in stages: the first meaningful cutoff arrives on November 23 (mobile), and desktop follows on December 22, 2026. Dia carries over several recognizable Arc features and supports migration of key browser data, but you should test the new setup instead of assuming everything will feel the same.
If you rely on Arc, start the migration while you still have access. Check the company's shutdown announcement and current instructions, move the data you need, and verify the result in Dia (or another browser). A little testing now is a lot cheaper than discovering a missing password, extension, or work setup after the old browser is gone.