Skip to main content
Export everything downloads your documents, job applications and Career data in one zip, including version history and referenced uploaded files. Check the file manifest for omissions. Use the archive as a backup, to keep a record before deleting your account, or to take your data elsewhere.

Download the archive

1

Open Your data

Select your name at the bottom of the sidebar, then Settings. On the Account page, scroll to Your data.
2

Select Export

Next to Export everything, select Export. Your browser downloads a file named reactive-resume- followed by today’s date, for example reactive-resume-2026-09-30.zip. While the archive is preparing, Cancel stops the export.
Account settings for fictional Alex Morgan

Account controls and your data

What’s in the zip

In applications.json, appliedAt is filled in even for a job you only saved: it starts as the date you saved it. status is the current stage. submittedAt is the first recorded submission time, or null when no submission is recorded. It stays set if you later return the job to Saved or close it. This records what you tracked in Reactive Resume; it does not confirm delivery to an employer. Older server exports may omit submittedAt; a missing field does not prove that you never applied. career.json contains your preferences, facts and their source/correction history, stories, reviewed reusable answers with scope, source and evidence revision references, workspace answers and checklist state, saved results, schedules, notifications, discovered roles, voice transcripts, and career conversations with attachment metadata. Referenced live attachment files are saved separately under uploads/. Raw voice recordings are not retained or exported. It also includes aiRequests (recorded request attempts, action, connection label, provider type, requested model and timestamp) and writingReviews (saved wording reviews and their source references). Saved letters and their history include private operation references that link to these records; portable letter JSON omits them. Usage records contain no prompts, credentials, provider endpoint URLs, token counts or cost estimates. Deleting a saved connection preserves these historical records; deleting the account removes them. Each resume and letter file is named after the document plus a unique ID, so two documents with the same name don’t overwrite each other. The archive doesn’t include your password, passkeys, two-step verification codes, API keys or AI provider keys. Document JSON keeps its original image addresses; upload-manifest.json maps included stored files to their paths inside the archive. External image addresses remain references: the export never downloads files from another website. Unreferenced files and deleted conversation attachments are excluded, including bytes left behind by a failed cleanup.

Check file coverage before deleting an account

The export reads at most 500 referenced stored files, including failed attempts. Each file can be up to 8 MiB, with 16 MiB of uploaded bytes in total. The complete archive can contain up to 64 MiB before compression and 50,000 entries, including document and history records. These limits keep preparation bounded on web, native and self-hosted servers. Files that are missing, unreadable, too large, outside your account, from an external storage address, or beyond the read or byte budget appear in upload-manifest.json with a reason. Stale conversation file references are marked not-live-attachment and never read. If files were skipped, the app also shows a warning after the download or share. An archive that exceeds its overall size or entry limit fails visibly rather than downloading a partial set of records. Individual document exports contain only that resume or letter; they omit applications, Career data, feedback and AI content reports. Keep copies of all records you need before deleting your account. If the complete archive fails, do not treat individual exports as a full account backup. Open the manifest before deleting your account. Keep any skipped files separately. Included file bytes and version records remain readable after account deletion; remote addresses may stop working. Restoring an individual document does not automatically upload the archived photos or attachments again: select those files manually where needed. An older server can still export the original JSON archive. If the app warns that the server exports file references only, update the server before relying on the archive to keep uploaded files.
To restore a resume or letter, extract the archive and import its individual JSON file from resumes/ or letters/. Resume content and design are restored as a new document; account settings, document sharing settings and application links are not restored. The whole zip is an account backup, not a bulk-import file. You can also download one resume as JSON from the arrow beside Download PDF. See Importing resumes.
On native mobile, Export everything shares the same zip, with the same files, so you can extract it and import individual resumes and letters the same way. Export saved profile under Profile → Manage profile shares only that record. Private profile exports do not import into a resume. These files contain personal information; choose their destination deliberately. Temporary mobile export files are removed on the next export, profile deletion, app startup, sign-out or session expiry. Signing into another account also clears them. Copies saved by a share recipient remain outside the app. MCP account export keeps file references only and excludes the private application profile and uploaded bytes. Use Settings → Account → Export everything for the full archive, or Settings → Application profile on web for the private profile.