Where Claude saves the files it makes and why downloads go missing: /mnt/user-data/outputs explained

1 hour ago

9 min read

Last verified: November 7, 2026

When Claude builds a spreadsheet, a slide deck, a Word document or a chart for you, it does the work on a small private computer that Anthropic starts for each conversation, and only the files it hands back at the end show up as download cards in the chat. Most cases of a "missing" file come from that hand-off: Claude finished the work but left the file in its own working folder, the file is larger than the download cap, the conversation was shared with someone who cannot see files, or the feature that lets Claude create files is switched off for your account or organization.

The short answer is ask Claude to save the final file to its outputs folder and present it again, then download it before you close the chat. The folder that feeds the download list is reported as /mnt/user-data/outputs, a path Anthropic does not document but which independent write-ups and Claude's own descriptions of its environment agree on. The behavior covers the Free, Pro, Max, Ultra, Team and Enterprise plans on the web, Claude Desktop and the Claude mobile apps, since Anthropic's help center lists file creation on all of them.

··········

WHAT CLAUDE USERS SEE WHEN A CREATED FILE GOES MISSING.

The symptom rarely comes with an error message, which is why it confuses people. Claude writes in the chat that the report or workbook is ready, sometimes with a file name in the text, but no download card appears below the reply and nothing new shows up in the list of files for that conversation. In other cases a card does appear, yet the file you download is an older version that lacks the changes you asked for in the last few messages.

A second pattern appears when someone else opens your conversation. Anthropic's help article on file creation states that public sharing is disabled for conversations that contain file artifacts on the Free, Pro, Max and Ultra plans, so a colleague cannot pick up a workbook through a shared chat link the way they could read a text answer.

A third pattern belongs to very long chats. On paid plans with code execution enabled, Claude condenses earlier messages as the conversation approaches its context limit, and Anthropic says the full history is kept so Claude can still refer back to it. Anthropic does not say how this condensing treats files created before it, so a file made early in a very long chat is best downloaded before the conversation grows much further.

··········

HOW CLAUDE'S FILE SANDBOX IS ORGANIZED.

Anthropic describes the environment in general terms: an isolated, sandboxed container for each user, with limited task duration, a limited container lifetime and intentionally limited storage and network resources. It does not publish the folder layout. The paths below come from two independent technical write-ups (a developer post on DEV Community in January 2026 and a security research post from Bishop Fox dated October 29, 2026), both based on Claude listing its own environment, plus one GitHub issue about Claude Desktop.

........

Folder	What it holds	How it is known
/mnt/user-data/uploads	Files you attach to the chat, mounted read-only	Two independent write-ups
/mnt/user-data/outputs	Files Claude hands back to you; this is what feeds the download cards	Two independent write-ups
/home/claude	Claude's working folder for drafts, scripts and intermediate files	Two write-ups; not shown in the download list
/mnt/skills	Read-only instructions Claude uses for Word, Excel, PowerPoint and PDF files	One security write-up
/mnt/transcripts	Full text of a long chat after it was condensed, seen in Claude Desktop	One GitHub issue, March 2026

........

The working folder and the outputs folder are the two that matter for downloads. The DEV Community author observed that Claude usually drafts a file in /home/claude and then presents it, which places a copy in /mnt/user-data/outputs; a file that stays only in the working folder can be opened from the tool output in some cases but does not appear in the conversation's file list. The same author saw a second consequence: with two copies on disk, Claude sometimes edits the working copy while the download card keeps pointing at the older copy in outputs.

··········

WHY CLAUDE DOWNLOADS DISAPPEAR: CAUSES, CHECKS AND FIXES.

........

Cause	How to check	Fix
File left in the working folder, never presented	Claude names the file but no download card appears	Ask Claude to copy the final file into /mnt/user-data/outputs and present it
Download card points at an older copy	Downloaded file lacks the latest edits	Ask Claude to overwrite the copy in outputs and present it again
File larger than 30 MB	Ask Claude to report the file size	Ask for a smaller file: split it, compress images, or drop raw data
File creation switched off	Settings > Capabilities shows "Create and edit files" off	Turn it on, or ask your organization's owner to enable it
Container reset during a long or idle session	Claude reports the file or folder no longer exists	Ask Claude to rebuild the file from the chat, then download it at once
Conversation opened through a share link	The viewer sees text but no file cards	Send the file itself or save it to Google Drive and share that
Linked Personal Finance accounts used in the chat	The chat used Claude's Personal Finance feature	Start a new chat for the file task
Usage limit reached before the file was saved	A limit message appeared mid-task	Wait for the reset or use usage credits, then ask Claude to finish and present the file

........

The 30 MB cap, the settings switch, the share-link restriction, the Personal Finance limitation and the higher usage cost of file creation are all stated in Anthropic's help article. The working-folder and stale-copy causes rest on the observations of the two write-ups described above, so treat them as reported behavior rather than documented rules.

··········

STEP-BY-STEP FIXES FOR MISSING CLAUDE FILES.

For a file that Claude says it made but that never appeared:

1. Reply in the same chat and ask Claude to list the contents of /mnt/user-data/outputs and of its working folder, with file sizes.

2. If the file sits only in the working folder, ask Claude to copy the final version into /mnt/user-data/outputs and present it as a downloadable file.

3. Download it right away from the card below the reply, or use the Google Drive option if you want a copy outside the chat.

4. If the listing shows the file is above 30 MB, ask for a lighter version before downloading.

For a download that contains an old version:

1. Ask Claude which copy it edited last and to overwrite the file in /mnt/user-data/outputs with that version.

2. Ask it to present the file again, then download the new card rather than an earlier one higher up in the chat.

3. Open the file and check that the last change you requested is there before you close the conversation.

For a file that no longer exists in the sandbox:

1. Ask Claude to confirm whether the file is still on disk.

2. If it is gone, ask Claude to recreate it from the instructions and data already in the chat; the uploads you attached earlier may also need to be attached again.

3. Download the rebuilt file as soon as the card appears.

When Claude cannot create files at all, open Settings, then Capabilities, and check the "Create and edit files" switch (labelled "Code execution and file creation" in the older layout). On Team and Enterprise plans the switch lives under Organization settings, then Capabilities, and only an owner can change it, along with the network access options for the sandbox.

··········

CLAUDE ON WEB, DESKTOP AND MOBILE: WHAT DIFFERS.

........

Platform	Where the file appears	What download does
Claude on the web	Download card under the reply and the chat's file list	Saves the file through the browser
Claude Desktop (Windows, macOS)	Same cards and file list as the web	Saves the file to your computer
Claude for iOS and Android	Download card under the reply	Opens the file in the system preview or another app, such as Word for a .docx
Any platform with Google Drive connected	Option to save to Drive	Writes a copy to your Drive

........

Anthropic's help article gives the mobile settings path as your initials or name in the left sidebar, then Settings, then Capabilities. On a phone a tap on Download hands the file to the system preview or another app, so the file still has to be saved from that app if you want to keep a copy on the device.

Claude Desktop also has a separate way of working with files on your own disk through local connectors. Those files live on your computer and follow its rules; the sandbox folders in this guide belong to Anthropic's cloud environment and are separate from your local drive.

··········

THE CLAUDE API EQUIVALENT: $OUTPUT_DIR AND THE FILES API.

Developers who call the code execution tool directly get the same design in documented form. The Claude Platform documentation says each bash_code_execution call receives a new, empty directory available as $OUTPUT_DIR; files at the top level of that directory are captured when the command finishes, and files written anywhere else stay in the container and are not returned. Each captured file comes back with a file_id that the Files API can download, and those files persist until they are explicitly deleted.

The documentation also gives the limits of the container itself: containers expire 30 days after creation, an idle container is checkpointed after about five minutes and can be restored with its ID inside the 30-day window, and container data is retained for up to 30 days. The retrieval pattern published in the docs is:

for item in response.content:
    if item.type == "bash_code_execution_tool_result":
        content_item = item.content
        if content_item.type == "bash_code_execution_result":
            for output_block in content_item.content:
                file_id = output_block.file_id
                meta = client.files.retrieve_metadata(file_id)
                client.files.download(file_id).write_to_file(meta.filename)

The docs recommend ending the command by copying the finished file into $OUTPUT_DIR and listing it, so the output confirms the capture. These API rules are documented for the developer platform; Anthropic has not said that the claude.ai app uses the same timings.

··········

WHAT ANTHROPIC DOCUMENTS AND WHAT ONLY USERS REPORT.

........

Claim	Status
Files can be downloaded throughout the conversation	Documented in the help center
30 MB maximum per file, for uploads and downloads	Documented in the help center
Container lifetime and task duration are limited	Documented, without figures for claude.ai
Public sharing disabled for chats with file artifacts (Free, Pro, Max, Ultra)	Documented in the help center
File creation uses more of your plan's usage limits	Documented in the help center
Long chats are condensed on paid plans with code execution	Documented in the help center
/mnt/user-data/outputs feeds the download list	Reported by two independent write-ups
Files left in /home/claude do not appear in the file list	Reported by one developer write-up
Full transcripts saved to /mnt/transcripts after condensing	Reported in one GitHub issue (Claude Desktop)
API: only $OUTPUT_DIR files are returned; 30-day container expiry	Documented for the Claude API

........

The folder names are internal details that Anthropic could rename without notice, so the reliable part of the advice is the principle behind them: a file reaches you only when Claude places it where the app collects downloads and presents it in the reply.

··········

KEEPING CLAUDE FILES SAFE AFTER EACH SESSION.

The simplest protection is to download or save to Google Drive every file you intend to keep as soon as its card appears, since Anthropic promises availability during the conversation and nothing beyond it. For work that goes through many revisions, ask Claude at the start to keep only one copy of the final file in the outputs folder and to present it after every change; this removes the stale-copy problem the developer write-up describes.

For long projects, a new chat for each major deliverable keeps the context smaller, avoids the condensing step and costs less of your usage limit. When you return to an old chat, check whether the download cards still open before you depend on them, and attach your source data again if Claude can no longer read it. Readers who also use ChatGPT will recognize the pattern from our guide to ChatGPT's "file is no longer available" error, where files in the /mnt/data folder expire on a fixed timer. The size caps for what you can attach are covered in our guide to Claude file upload limits, and copies of whole conversations can be taken through the account export described in our guide to opening a Claude data export.

··········

CLAUDE FILE STORAGE: WHAT IS SETTLED AND WHAT IS NOT.

Anthropic's own pages settle the practical limits: file creation is available on every consumer and business plan, files stay downloadable for the life of the conversation, each file is capped at 30 MB, shared chats do not carry files on individual plans, and the sandbox has a limited lifetime. The folder map with /mnt/user-data/uploads and /mnt/user-data/outputs is consistent across independent write-ups from January and October 2026, while the claim that files left in the working folder never reach the download list rests on one detailed report.

What Anthropic has not published is how long a claude.ai sandbox lives, whether a file in the outputs folder survives a container reset, and how condensing a long chat treats files created before it. Until those details are documented, the safe practice is simple: ask Claude to present every final file from its outputs folder, download it the same day, and keep your own copy outside the chat.

··········

·····

DATA STUDIOS

·····

datastudios.org