How to Back Up and Transfer CapCut Projects Safely

To move a CapCut project without losing its editable layers, upload the project to an available Space and open it on the destination device. Keep the original until you've checked the transferred timeline, source media and export. For a desktop backup, also copy the complete draft folder and its source files to separate storage. Just don't mistake that file copy for a proven transfer.

What to keep before you move the project

You need the editable draft and the media it uses: video, photos, voiceovers, music and graphics. If the original can export, keep a reference video too. Add a short note with the CapCut version, operating system, font names and any paid or licensed assets the next editor will need.

Choose the route that fits the move

Back up and transfer through Spaces

CapCut's saved-project instructions describe Spaces for cross-platform access. Signing in doesn't mean every local draft got uploaded, so check the specific project.

1. Save the edit on the source device. Return to its project library after saving normally. Keep the original and its media intact.
2. Upload the editable project. Use the project's available Upload, Project sync or Space control. Select the intended Space and check upload permission and available storage. Uploading an MP4 as media is not the same operation.
3. Wait for the upload to finish. Keep the app and connection available. Resolve any upload or quota error before relying on the cloud copy.
4. Open that Space on the destination. Use the owning account, or an accepted invitation with edit access when handing the project to someone else. Open the project as an editable timeline.
5. Verify a working duplicate. Follow the full checklist below: timeline, copied media, fonts and effects, saving, and export. Keep the original while you check the result.

Check capacity before a large upload. According to CapCut's new-Space storage notice, newly created Spaces get no complimentary capacity and may show a 1 KB placeholder. Existing accounts and purchased storage can differ. Go by the allowance your Space displays, not an old tutorial's 5 GB meter.

When a Space won't load, check the selected account, your connection and that you're on a supported app version. Preserve local drafts before an update. On its own, a Space you can't open isn't evidence that the project was deleted.

An empty account may be the wrong account

Google sign-in and email-and-password sign-in can lead to different CapCut accounts, even when the email address looks identical. Follow CapCut's cross-device login instructions and use the original method, or a login you deliberately linked to that account. QR sign-in from your signed-in phone can get you into the account, but it doesn't upload local drafts.

Keep the old device signed in while you check. If the new device shows an empty library, retry the original login route there instead of deleting either account. Our CapCut login guide covers account-access problems.

Back up desktop files without cloud storage

This preserves files; it is not a universal restore procedure. A draft can depend on source files that live outside its folder. If you don't know which folder belongs to the project, find its actual draft location first. An older edit may not be in the current default save folder.

1. Save the working project and close CapCut normally. Do not change the save-location setting as a migration step.
2. Copy the complete draft folder to a dated folder on separate storage. Copy it rather than moving the only version, and do not overwrite another project library.
3. Copy its source video, audio, photos and graphics too, preserving filenames and subfolders. Open a selection of the copied files to check that they are usable files rather than cloud placeholders.
4. Add the reference export, if available, and the version, font and asset notes. Keep this archive separate from the device you plan to replace.

What if the copied folder does not appear on the new computer? Leave both copies intact. Having the folder in place doesn't register a project or repair file paths. Even the third-party CapShare project's packaging documentation describes path and project-index work that goes beyond copying files. Take that as evidence of the dependencies, not as a recommendation to install an unverified third-party tool.

Don't rename draft JSON files, merge libraries or overwrite a project index to force the edit open. A ZIP can preserve files without being a package CapCut can import. If your installed version has no documented import route for the copy, fall back on a working Space transfer from the intact original, or ask CapCut support about that specific version.

A newer draft may also be incompatible with an older app. Even matching version numbers don't guarantee matching fonts, effects or account access, so test on the destination before you give up the working installation.

Moving to a new iPhone or Android phone

When project upload is available, use the Spaces procedure above and save the original camera clips separately. Keep a phone backup as an extra safeguard, but I wouldn't treat it as proof that the CapCut timeline will restore. Apple includes eligible app data in iCloud Backup, while Google explicitly warns that not all apps back up or restore all their data.

A file sitting in iCloud Drive or Google Drive isn't the same as a device backup. Neither route turns an arbitrary draft folder into a supported cross-platform import. Modern Android also restricts access to app-data folders, so don't rely on an old file-manager tutorial.

Don't uninstall as part of the transfer. Android removes app-specific files on uninstall, and Apple's Delete App action removes related data. Offload App keeps data on that iPhone, but it isn't a second copy. If the new phone can't reproduce the edit, keep the old one intact.

Handing the editable project to another person

Invite the recipient to the intended Space, then check that they accepted with the correct account and have an editing role. A pending invitation or a view-only link isn't enough. CapCut's Teams access guidance explains the membership requirement.

If your editor offers Transfer editing permission, the documented handoff goes like this: open the project, open its … menu, choose that command, select the recipient and confirm. Before you leave, ask them to open and edit a duplicate. Don't assume every plan or editor supports simultaneous editing; check the controls both of you have.

Agree on who owns the Space, who keeps the archive, which export is the approved reference, and whether the recipient can use the required fonts, music and paid assets. If you're leaving a team, preserve only the work you're authorized to keep, because leaving can remove access to team projects and assets.

Why the MP4 is not enough

An exported MP4 holds the rendered picture and sound. It doesn't carry the original editable text, masks, keyframes or audio tracks. CapCut's instructions for reusing an exported edit explain that it comes back as one clip. Keep a reference export for comparison, but don't send it when the recipient needs the original layers.

Check the project on the destination

Run these checks on a working duplicate, not on your only original or a teammate's live edit. An early sample export can catch problems fast, but it can't verify the rest of a long project.

1. Review the full timeline. Compare duration, layers, captions and transitions with the original. Inspect every section, from the opening frame to the end.
2. Check the copied media. Confirm the destination can use the preserved source files. A project reopened on the old computer may still be reading the originals. Do not delete or rename those originals just to test the backup.
3. Check fonts, effects and access. Look for substitutions, missing downloads and unavailable paid assets. The recipient needs their own appropriate access and usage rights.
4. Test saving. Make a harmless change to the duplicate, close it normally, reopen it and confirm that the change remains.
5. Compare the export. Start with a difficult section containing captions, overlays, speed changes and layered audio. Watch it outside CapCut beside the reference, if available. Review the full final export before delivery or retiring the old device.

One real PC-to-phone transfer report describes missing video after the user uploaded a project to a Space. The cause wasn't established, but the case shows why a finished upload isn't the last check.

If clips are missing, keep both copies. Use a relink control only if your build has one, run it on a duplicate, and point it to the copied source files. Re-importing clips doesn't guarantee their old timing comes back. While you investigate, don't delete placeholders or overwrite the original.

Keep an archive after the move

Keep dated copies of the project and media somewhere other than the device you might erase. Don't overwrite your only known-good archive every time you save an edit. CapCut’s autosave protects work in progress, not necessarily an earlier version you want back.

A synced Space isn't an independent archive either, since CapCut says deleting a Web project affects linked devices. Hold on to a separate recovery point and recheck important archives now and then, especially before you change devices or app versions.

Frequently asked questions