ChatGPT Atlas Shuts Down August 9. What Happens To Your Browser History And Cookies?

August 9, 2026

ChatGPT Atlas stops August 9. Learn what transfers, what stays separate, and how to protect browser history, cookies, sessions, and memories.

OpenAI says ChatGPT Atlas is scheduled to stop working on August 9, 2026. If you used Atlas, do not assume moving to ChatGPT, Codex, Chrome, or another browser will bring everything with you. OpenAI says bookmarks, open tabs, and browser history will not transfer automatically. ChatGPT conversations are separate, while cookies and session files are sensitive and may not have a supported import path.

Watch The 30-Second Summary

Watch this video on YouTube

The urgent task is not simply choosing a new browser. It is deciding which Atlas data you need to preserve, which account data will remain available, and which sensitive local records you should deliberately delete rather than carry forward.

What Is Confirmed

OpenAI's current Atlas migration guide confirms the August 9 deadline and several important data boundaries.

• Atlas may stop opening or browsing after the deadline. OpenAI says it may no longer support browser-based agentic workflows and recommends moving to a supported browser experience before August 9.
• Bookmarks do not transfer automatically. OpenAI tells users to export them as an HTML file and import that file into another browser such as Chrome.
• Open tabs do not transfer automatically. Users should bookmark important tabs, copy their URLs, or save the pages another way.
• Browser history does not transfer automatically. OpenAI recommends saving or bookmarking pages a user may need later.
• Cookies and session files are sensitive. Atlas may provide export options where available, but OpenAI warns not to share those files unless the recipient is trusted and the user understands what access they may provide.
• Active sessions cannot simply be imported into another browser. OpenAI's troubleshooting section says cookies and active sessions cannot be imported into another browser.
• ChatGPT conversations are separate from Atlas browser data. OpenAI says existing ChatGPT conversation history remains available through ChatGPT, subject to the user's plan, workspace settings, and account access.

The shutdown therefore is not a single database migration. It is a collection of different local and account-side stores with different preservation, import, and deletion behavior.

What Is Still Unclear

OpenAI's public migration guide does not answer every post-shutdown question.

It does not promise that the Atlas application will remain usable as an offline viewer after August 9. It says Atlas may no longer open or browse, which is a reason to export before the deadline rather than expecting continued access.

It also does not document:

• the exact Atlas version or operating-system conditions under which cookie export is available;
• whether every cookie export preserves the same fields or encryption protections;
• a supported way to import active Atlas sessions into another browser;
• whether browsing history has a complete export format beyond manually saving important pages;
• how long an installed Atlas profile remains on the device after the service stops;
• whether uninstalling Atlas automatically removes every local profile file;
• a special shutdown retention schedule for Atlas-specific server data;
• whether every Browser memory or diagnostic record is automatically deleted because Atlas is discontinued.

Absence of a transfer path is not proof of deletion. A record can fail to migrate and still remain in an old local profile, account control, backup, server log, or exported file. Users who care about removal need to use the documented deletion controls and inspect the device rather than treating discontinuation as an erasure event.

The Six Data Stores Atlas Users Should Separate

The phrase "my Atlas data" is too broad to guide a safe migration. At least six stores matter.

• Bookmarks: No automatic transfer. Export bookmarks as HTML and verify the file opens or imports so saved pages are not lost.
• Open tabs and browser history: No automatic transfer. Bookmark or copy important URLs; do not assume a full research trail will migrate.
• Cookies and signed-in sessions: No supported general import path. Avoid sharing cookie exports, which may expose account access, and sign in again normally in the new browser.
• Passwords, autofill, downloads, and site settings: The shutdown guide does not promise a transfer. Review Atlas advanced settings and use only supported, trusted export paths so credentials and sensitive form data are handled deliberately.
• Atlas Browser memories: Separate from cookies and ChatGPT Memory. Review or archive Browser memories, and delete related Web History when removal is the goal.
• ChatGPT conversations and ChatGPT Memory: Separate from Atlas browser data. Manage chats and Memory through ChatGPT's own controls rather than assuming browser cleanup deleted them.

This separation prevents two opposite mistakes: losing useful information because it was never exported, and carrying sensitive account or browsing material into a new environment without understanding it.

What Happens To Atlas Bookmarks?

OpenAI says Atlas bookmarks will not transfer automatically. Its supported migration steps are straightforward:

1. Open Atlas before the deadline.
2. Open the bookmarks menu or bookmark manager.
3. Choose the bookmark export option.
4. Save the resulting HTML file in a location you can find.
5. Import the HTML file into a supported browser.

An exported bookmark file is readable data. It can reveal medical research, financial concerns, client projects, internal tools, private communities, travel plans, political interests, and other browsing patterns through page titles and URLs.

Treat the file accordingly:

• store it in a folder protected by the device account;
• do not attach it to a public support ticket or community post;
• remove bookmarks you no longer want before importing;
• import it into the intended browser profile, not a shared profile;
• delete unnecessary export copies after verifying the new browser contains the expected bookmarks.

The HTML export is a migration artifact, not a harmless formatting file.

What Happens To Open Tabs And Browser History?

Open tabs and browsing history are not the same as bookmarks.

OpenAI says tabs may not transfer automatically. A tab can represent unfinished work even if the page was never bookmarked: a partially completed form, a research result, an account setting, a draft, or a page reached through a temporary search.

OpenAI also says browser history will not transfer automatically. That means a user who depends on history search to recover old research should not expect another browser to reproduce the same timeline.

Before the cutoff:

• close irrelevant tabs so the remaining set is easier to inspect;
• bookmark pages worth keeping;
• copy one-off URLs into a private note if they do not belong in permanent bookmarks;
• save unsent form text or drafts in the owning service, not only in the browser tab;
• record the title and URL of research pages whose content may change;
• verify important downloads exist outside the browser's temporary state.

Do not use a screenshot as the only backup for a URL-heavy research session. A screenshot may preserve visible context but not a usable link, full title, login state, or page content.

Can You Move Atlas Cookies Or Logged-In Sessions?

Do not plan on it.

OpenAI says Atlas will provide cookie export options where available, but it also says cookies and active sessions cannot be imported into another browser. Those statements are not necessarily contradictory: a product can let a user export data without another browser supporting a safe import of live authenticated sessions.

Cookie or session material can function like account access. A person who obtains a usable session token may be able to act as the signed-in user without knowing the password, depending on the site and its protections.

The safer transition is usually:

1. Install or update the supported destination browser from its official source.
2. Sign in to each important site through its normal login page.
3. Use a password manager or passkey flow you already trust.
4. Complete multifactor authentication normally.
5. Review active sessions on high-value accounts.
6. Sign out Atlas sessions you no longer need.

Do not upload a cookie database or session export to a random converter, migration website, chatbot, shared drive, or public issue. Do not email it to yourself unencrypted merely because the file is difficult to import.

What About Passwords, Autofill, Downloads, And Site Settings?

OpenAI's Atlas data-controls guide lists several additional categories in advanced deletion settings:

• download history;
• passwords and other sign-in data;
• autofill form data;
• site settings;
• cookies and other site data;
• cached images and files.

The shutdown guide does not promise that all of these categories transfer to ChatGPT or a new browser.

Download history is especially easy to misunderstand. Deleting a browser's download-history list may remove the record from the browser without deleting the downloaded file from the device. Conversely, preserving the history list does not guarantee the file still exists.

Inspect the actual Downloads folder and any project folders. Move files you intend to keep into an appropriate location, scan unfamiliar downloads, and delete sensitive or unnecessary files deliberately.

Autofill deserves similar care. It may include names, addresses, phone numbers, payment-related form data, or other details. Migrating a whole profile for convenience can also move information you would not choose to re-enter manually.

What Happens To Atlas Browser Memories?

Atlas Browser memories are not ordinary browser history, cookies, or ChatGPT Memory.

OpenAI's current Atlas data-controls and privacy guide says Browser memories can remember useful facts and insights from browsing. When enabled, web content can be summarized on OpenAI's servers; OpenAI says it deletes page content after summarization and deletes privacy-filtered summaries within seven days. Supported macOS 26 users may have an on-device summarization option.

OpenAI says users can:

• turn Browser memories on or off;
• view Browser memories;
• archive memories they do not want referenced;
• delete Web History to delete associated Browser memories;
• disable ChatGPT visibility for specific pages.

The shutdown announcement does not say every Browser memory will automatically disappear on August 9. If removal matters, use the documented controls before losing reliable access to Atlas settings.

Archiving a Browser memory and deleting it are also different actions. OpenAI describes archive as a way to stop a memory from being referenced, while deleting related Web History removes associated Browser memories. Users should decide whether they want a detail hidden from personalization, removed from the relevant history, or retained for future use.

Does Deleting ChatGPT Chats Delete Atlas Browser Data?

No. OpenAI explicitly says deleting all chats does not delete Browser memories, cookies, or other Atlas-specific data.

This boundary works in both directions:

• clearing Atlas browsing history is not the same as deleting ChatGPT conversation history;
• deleting ChatGPT conversations is not the same as deleting Atlas cookies or Browser memories;
• turning off ChatGPT Memory is not the same as clearing Atlas Web History;
• uninstalling a browser is not documented as an account-wide ChatGPT deletion action.

OpenAI says ChatGPT conversations remain available separately after Atlas is discontinued. That is useful if you want to keep conversations, but it also means moving away from Atlas should not be treated as a ChatGPT privacy reset.

For a related separation between browser data and account history, read ChatGPT Temporary Chat Vs Browser-Local AI History.

Does The Atlas Shutdown Delete Data Automatically?

OpenAI has not made that broad promise.

The documented event is a product discontinuation. OpenAI says Atlas may stop opening, browsing, and supporting browser-agent workflows. It does not say the shutdown is equivalent to deleting every local profile, account conversation, Browser memory, diagnostic record, cookie, password, cache entry, or downloaded file.

Deletion remains category-specific:

• Web History has its own deletion control.
• Browser memories are tied to related Web History and have their own archive view.
• ChatGPT chats use ChatGPT controls.
• cookies and site data use browser controls.
• downloaded files live outside a browser-history list once saved to disk.
• exported bookmarks and other migration files remain wherever the user stores them.

If your goal is erasure rather than migration, create a deletion checklist for each category and verify the result. Do not assume the shutdown date performs that work for you.

The MAPS Migration Check

Use the MAPS check before Atlas stops working.

M - Mark what matters

Identify the bookmarks, tabs, research trails, downloads, and ChatGPT conversations you actually need. Avoid copying an entire profile merely because selective review takes time.

A - Account data is separate

Treat ChatGPT chats, ChatGPT Memory, Browser memories, third-party website accounts, and local browser data as separate stores. Confirm each through its own settings.

P - Protect portable files

Bookmark exports, password exports, cookie databases, session files, and copied URLs can all expose sensitive activity or access. Store them carefully, minimize copies, and never use untrusted conversion services.

S - Scrub what should not follow you

Delete unwanted Web History, Browser memories, cookies, autofill data, downloads, and export files using the correct category-specific control. Verify before uninstalling or losing access to Atlas.

MAPS is useful beyond this shutdown. Any browser or AI-workspace migration can fail when users treat visible tabs, local profile data, and cloud account data as one object.

A Practical Atlas Exit Checklist

Complete the preservation steps first, then deletion. Deleting too early can remove the source you needed to audit.

Preserve

• Export Atlas bookmarks to HTML.
• Open the exported file and verify that expected folders and URLs are present.
• Bookmark or copy important open-tab URLs.
• Save unfinished work in the service that owns it.
• Locate downloaded files on disk.
• Record any browser extensions, site permissions, or workflow settings you need to recreate.
• Confirm that necessary ChatGPT conversations remain visible in ChatGPT.

Re-establish access safely

• Install the destination browser or ChatGPT app from an official source.
• Import only the supported bookmark file.
• Sign in to sites normally rather than moving opaque session files.
• Review multifactor authentication and recovery methods.
• Check high-value accounts for unrecognized active sessions.

Review and remove

• Inspect Atlas Web History and Browser memories.
• Decide whether to archive or delete each relevant memory.
• Clear unwanted cookies, site data, cache, autofill, passwords, and site settings.
• Delete unneeded downloads from the filesystem, not just the browser list.
• Remove temporary bookmark exports after verifying the destination.
• Uninstall Atlas only after confirming preservation and cleanup.

Verify

• Search for several known bookmarks in the destination browser.
• Open a sample from each imported folder.
• Confirm copied URLs are complete.
• Verify ChatGPT conversations through ChatGPT, not through Atlas.
• Check whether old Atlas data remains in device backups or shared folders if that matters to your threat model.

Who Should Act First?

The deadline matters most to people who used Atlas as a primary work browser or enabled browsing personalization.

Prioritize the migration if you used Atlas for:

• client or employer research;
• medical, legal, or financial browsing;
• logged-in administrative tools;
• long-running research across many tabs;
• browser memories and personalized suggestions;
• password or autofill storage;
• agent mode on authenticated sites;
• separate personal, work, or school browser profiles.

Workspace administrators should also identify users relying on Atlas, distribute the migration deadline, document a supported replacement, and remind users that cookie and session files are credentials—not ordinary attachments.

What The Shutdown Does Not Prove

Atlas being discontinued does not prove that every AI browser is unsafe, that every Atlas user suffered a breach, or that ChatGPT conversations will disappear.

It also does not prove:

• that OpenAI will delete every Atlas record on August 9;
• that exported cookies are safe to share;
• that a bookmark import recreates browsing history or open tabs;
• that moving to Chrome, ChatGPT, or Codex reproduces the same data controls;
• that an old Atlas profile is secure indefinitely without browser updates;
• that OpenVeil can migrate, inspect, or delete Atlas data.

OpenAI warned at launch that browser agents can face hidden malicious instructions and that safeguards will not stop every emerging attack. That is a browser-agent risk boundary, not evidence that the shutdown was caused by a specific breach. OpenAI describes the change as moving browser-based agentic capabilities into ChatGPT and Codex.

Where OpenVeil Fits

OpenVeil is not an Atlas replacement browser. It cannot import Atlas bookmarks, cookies, sessions, history, passwords, or Browser memories.

OpenVeil is a privacy-focused hosted AI workspace for adults. For normal chat sessions, it keeps conversation history in the user's browser instead of maintaining a normal server-side chat-history record. That makes the history boundary easier to reason about, but it creates a related responsibility: clearing site data, switching devices, changing browsers, or losing the browser profile can remove or hide that local history.

Active OpenVeil requests still require processing by OpenVeil and necessary AI, search, upload, hosting, routing, security, billing, and infrastructure providers. Browser-local history is not fully offline processing, anonymity, zero logging, or protection from compromised devices, exported credentials, browser extensions, or unrelated account risks.

OpenVeil's one-time preview includes ten bounded chat, search, upload, voice, transcription, or single-image actions without a card. Paid plans begin at $10 per month and add the complete workspace, including video. The relevant comparison is narrower: if you want ordinary AI conversation history kept in the browser rather than a normal server-side chat-history record, OpenVeil offers that model without asking you to operate an AI browser.

Read What Browser-Local Chat History Means In An AI App before relying on that boundary.

Frequently Asked Questions

When does ChatGPT Atlas shut down?

OpenAI says Atlas is scheduled to stop working on August 9, 2026. The company recommends exporting or saving important data before that date.

Will Atlas bookmarks move to ChatGPT or Chrome automatically?

No. OpenAI says bookmarks will not transfer automatically. Export them as an HTML file and import that file into a supported browser.

Will Atlas browser history transfer automatically?

No. OpenAI says browser history will not transfer automatically. Save or bookmark important pages before the deadline.

Will my open Atlas tabs transfer?

Do not assume they will. OpenAI recommends bookmarking important tabs or copying their URLs.

Can I import Atlas cookies or active sessions into Chrome?

OpenAI says cookie export options may exist where available, but active sessions cannot be imported into another browser and Chrome may not support a native cookie-import path. Treat any cookie or session export as sensitive credential material.

Will my ChatGPT conversations be deleted when Atlas stops?

OpenAI says ChatGPT conversation history is separate from Atlas browser data and remains available through ChatGPT, subject to plan, workspace, and account access.

Does deleting ChatGPT chats delete Atlas Browser memories?

No. OpenAI says deleting chat history does not delete Browser memories, cookies, or other Atlas-specific data.

Does deleting Atlas Web History delete Browser memories?

OpenAI says deleting Web History deletes associated Browser memories. It also says the change may take time to refresh.

Is uninstalling Atlas the same as deleting my OpenAI account data?

OpenAI's public migration guide does not say that. Browser installation, local profile data, Browser memories, and ChatGPT account data are separate layers.

Can I recover browser-local AI history after losing a browser profile?

Only if the app provides a separate sync, export, or backup path. Review Can You Recover Browser-Local AI Chat History After Clearing Site Data? for the broader recovery boundary.

Bottom Line

ChatGPT Atlas is scheduled to stop working on August 9, but its shutdown is not an automatic migration or a documented universal deletion event. Export bookmarks, save important tabs and URLs, locate downloaded files, and verify ChatGPT conversations separately. Treat cookies and session files like credentials, not ordinary browser data.

Most importantly, decide what should move and what should be deleted. Bookmarks, browsing history, cookies, Browser memories, passwords, downloads, and ChatGPT conversations follow different controls. A careful category-by-category exit is safer than copying everything—or assuming the shutdown erased it for you.