Arc Browser Stops Working December 22: Export Your Data Before It Is Deleted

Arc Browser Stops Working December 22: Export Your Data Before It Is Deleted.

Arc users need to act on a hard deadline. According to Arc’s official farewell and help-center notice, Arc for macOS and Windows stops working on December 22, 2026. Accounts are deactivated that day, associated personal data is deleted within 30 days, and after December 22 the company says it can no longer identify or retrieve Arc user data for data requests. If you use Arc on desktop, this is not just a “wrap-up later” situation; it is a data-migration deadline.

The most important point is simple: export now, verify what was actually exported, and back up anything critical independently. Do not assume that a saved list of tabs contains bookmarks, passwords, history, extensions, or every piece of browser data you care about.

The official shutdown timeline

October 22, 2026: New Arc accounts stop. Existing accounts continue to work. The latest desktop Arc version adds export tools and Dia import support.
November 23, 2026: Arc Search AI features stop on iOS and Android. Sign-in and tab sync stop on mobile.
December 22, 2026: Desktop Arc stops working. Accounts deactivate. The Android app is fully deprecated and removed. iOS keeps only a lite browser experience, as described by Arc.
After December 22: Arc says it can no longer identify or retrieve Arc user data for data requests. Personal data is deleted within 30 days.

What you should export, and what you should back up separately

Start by separating your browser data into three buckets.

Open tabs and spaces: useful for recreating your current workspace and moving into another browser or into Dia.
Bookmarks, passwords, history, and extensions: these may be available through official migration paths or browser-specific sync/export tools, but they are not the same as a tab export.
Critical information you should back up on its own: password-manager vaults, recovery codes, payment-related login details, work-managed credentials, important downloads, and any business notes tied to browser workflows.

If you only export tabs, you are saving a snapshot of browsing state. That is helpful, but it is not a complete account archive.

Official export steps: macOS and Windows

Arc’s desktop app is where the main export workflow lives. The official guidance in the release notes and farewell materials points users to the newest desktop build, which includes export and Dia import support. If you need an old installation, Arc says you can download it again from its official farewell page before December 22, then export inside the app.

macOS: Open Arc > Settings in the Mac menu bar > Advanced > Export Data > choose save location > Save.
Windows: press Ctrl+, or Arc menu > Settings > Advanced > Export Spaces and tabs > Export Data > choose save location > Save.
Export your tabs, spaces, and any available browser state using the built-in export flow.
If Arc offers a Dia import option in your build, use it only after you have reviewed what will be transferred and what will not.
Save the export file in a safe offline location, such as an external drive or encrypted local backup.

If your desktop build does not show the expected export menu, update first. If the menu is still missing, use the Help Center guidance from Arc’s release notes and sunset notice rather than guessing your way through older menus.

Official export steps: iOS

Arc on iOS does not keep the same long-term desktop feature set. Arc says iOS will retain only a lite browser experience after the shutdown milestones. Before November 23, and certainly before December 22, review anything you still need from mobile and move it into your new browser or saved archive.

Open Tab Switcher in the bottom-left > Settings > Export Data, then share or copy the list of open tabs.
Manually save important tabs, URLs, and account-related notes if you need something beyond the tab list.
Make sure your new browser or password manager has received anything essential before mobile sign-in and tab sync stop on November 23.

For iOS, a practical approach is to treat Arc as a temporary review point and move critical items out immediately rather than waiting for a later bulk export that may not exist for every data type. These mobile exports are lists of open tabs and are not full password, bookmark, or account archives.

Official export steps: Android

Arc’s Android app is scheduled to be fully deprecated and removed on December 22, with sign-in and tab sync ending earlier on November 23. That means Android users should not wait for the final shutdown date to start migration.

Open Tab Switcher (stacked-tabs button) in the bottom-left > Settings gear > Storage > Export data, then share or copy the list of open tabs.
Export or manually copy out important tabs and links.
If you rely on synced sign-in states, passwords, or workspaces, verify them in another browser or password manager before mobile sync ends.

If the app no longer signs in, you may lose the ability to trigger any cloud-dependent transfer workflow. Export first; troubleshoot later. These mobile exports are lists of open tabs and are not full password, bookmark, or account archives.

How Dia migration differs from a general browser backup

Dia is Arc’s official successor, and Arc’s migration materials present it as the direct next step for users who want the closest continuation of the Arc workflow. Arc’s company claims also describe Dia as faster and more secure, but that should be treated as the company’s claim rather than an independently verified benchmark here.

Migration to Dia is not the same as a generic browser backup. A successful move can include browser state and some familiar workflow elements, but you should still confirm the details yourself. In particular, do not assume every extension, password, profile setting, or workspace mapping will transfer exactly as you expect.

Do this in the right order

Update Arc to the latest desktop version.
Export tabs and spaces first.
Separately verify bookmarks, passwords, history, and any work-managed credentials.
Test a second browser before changing your default browser setting.
Keep the export file offline and labeled clearly.
Confirm extension availability and profile/workspace mappings in the new browser.
Sign out of Arc only after you have tested access to the migrated data.

Dia or another browser? A quick decision matrix

Use this as a practical checklist, not a ranking.

Choose Dia if you want the official successor path and the closest expected Arc-style migration experience.
Choose another Chromium-based browser if extension compatibility matters most and you want a familiar ecosystem.
Choose a browser with strong vertical tabs or workspace tools if your current Arc setup depends on structure more than visual style.
Choose a browser with stronger privacy controls if you want tighter data-minimization options and more explicit account control.
Choose a browser available on all the platforms you actually use if cross-platform continuity matters more than design.
Choose the browser that reduces account dependence if you want the least amount of vendor lock-in.

Only compare the features you truly need. A browser that looks closest to Arc may not be the best fit for your password flow, enterprise setup, or mobile routine.

Troubleshooting common problems

Old Arc install: update first. The export and Dia import features are described as part of the latest desktop Arc build.
Export menu missing: check that you are on the current version, then consult Arc’s Help Center release notes and sunset notice.
Mobile tab export: if a full export is unavailable, save critical tabs manually and move them before the November 23 mobile cutoff.
Work-managed passwords: these may be controlled by your organization, so verify with your IT admin or password-manager policy before assuming Arc can export them.
Account inaccessible: if you cannot sign in, prioritize any locally visible data and review Arc’s support guidance quickly, because the post-December-22 data request window is effectively closed.

What the deadline means in practice

The safest assumption is that Arc’s desktop shutdown is final, the mobile timeline is shorter than many users expect, and some data will not migrate automatically just because it exists inside your browser. If you use Arc for day-to-day work, treat this as a migration project, not a routine app update.

The best path is straightforward: update, export, verify, back up independently, test the replacement browser, and only then disconnect Arc from your workflow.

Sources

Arc official farewell and FAQ, Oct. 22, 2026: https://arc.net/
Arc Help Center release notes and sunset notice: https://resources.arc.net/hc/en-us/articles/20498285812375-Release-Notes
The Verge, Oct. 22, 2026: https://www.theverge.com/tech/1016832/arc-browser-shutting-down
Hacker News discussion: https://news.ycombinator.com/item?id=50197601