How to Back Up and Transfer CapCut Projects Safely

A safe CapCut backup has three parts: the editable project, the source media used by that project and a reference export. To transfer the project, put the editable copy in CapCut Spaces or copy the complete desktop project folder while CapCut is closed, then open the copy on the destination device and test it before touching the original.

Do not uninstall CapCut, reset the old device or delete the original clips yet. A project card, cloud icon or finished MP4 does not prove that the timeline can be edited somewhere else. The transfer is complete only after the second copy opens with its media, captions, effects and audio intact.

What we checked on August 9, 2026

We compared the current CapCut Desktop, Mobile and Web guidance for Projects, Spaces, account login and cross-device access. We also checked CapCut’s current rule for importing an exported video and recent reports from editors who lost access after a device failure, reinstall or incomplete cloud upload.

CapCut changes labels between builds and regions. Your app may say Space, Cloud, Project sync or Upload. The safety test does not change: open the second editable copy and play it before removing the first one.

The safest CapCut backup and transfer method

1. Open the original project. Scrub the full timeline and note any missing media, fonts or downloaded effects before you copy the problem.
2. Preserve the source files. Collect the videos, photos, voiceovers, music, fonts and graphics used in the edit.
3. Create a second editable copy. Upload the project to the intended CapCut Space or copy its complete desktop draft folder with CapCut closed.
4. Transfer or sign in on the destination device. Use the same CapCut login method, not merely the same email address.
5. Open and test the copy. Check the timeline, then export a difficult 20–30 second section with captions, effects and layered audio.
6. Keep both copies for a while. Do not erase the source device until the new workflow has survived at least one full open, edit, close and reopen cycle.

If you cannot find the editable folder or you are unsure whether a project is local or cloud-based, start with our guide to where CapCut saves projects on each platform. Finding the draft comes before copying it.

Choose the right transfer route

For most people, Spaces is the cleanest cross-platform route because it avoids guessing how an internal project folder should be registered on a different operating system. A manual folder copy is still useful as an extra desktop backup, but it should not be described as a universal project package.

How to back up a CapCut project to Spaces

CapCut’s own cross-platform project guidance says projects must be uploaded to Spaces for cloud use across devices. The same help page also uses broad language about projects saving to the cloud when you are logged in. Those two statements are easy to misread, so do not use login alone as proof of backup.

1. Connect to a reliable network and open CapCut on the device that holds the working project.
2. Return to the Projects screen. Find Upload, Project sync, Cloud or the menu that moves the project into a Space.
3. Select the intended Space. If you have personal and team Spaces, write down which one owns the project.
4. Leave the app open until the upload or sync indicator finishes. Large projects can take time, and a storage limit can stop the upload.
5. Open Spaces and confirm that the project card appears there.
6. Use another device or CapCut Web to open the project as an editable timeline. Do not stop at the thumbnail.

If a project appears in Local Projects but not in the chosen Space, treat it as local. If it appears in a Space but will not open elsewhere, treat the upload as unfinished or unverified. That distinction prevents the dangerous assumption that a cloud icon has already protected the job.

Use the same login method on the new device

CapCut supports several ways to sign in. The detail people miss is that Google sign-in and email-and-password sign-in can be separate CapCut accounts, even when both display the same email address. CapCut explains this in its current guide to using one account on multiple devices.

Before leaving the old device, record the login method that owns the Space: Google, email, TikTok or Facebook. On the destination device, choose that exact method. CapCut recommends QR login from the signed-in mobile app when moving to Desktop or Web because it reduces account mix-ups.

If the new device opens an empty account, do not upload a duplicate or delete anything from the old device. Sign out and try the original login route. Our CapCut connection checklist is useful when the correct Space exists but will not load.

How to make a manual desktop backup

A complete local copy is valuable when you work on Windows or Mac, especially before an update, disk replacement or long trip. It is also the part most tutorials oversimplify. CapCut project folders contain timeline data and references; they are not guaranteed to be a neat, portable document that works everywhere.

1. Open the project and confirm that it works on the original computer.
2. Use CapCut’s Settings → Draft/Project → Save to field to find the active folder. Do not rely on a path copied from an old tutorial.
3. Close CapCut completely. Wait a few seconds so the application finishes writing project metadata.
4. Copy the whole project folder to a dated backup folder on another physical disk or trusted storage location. Copy; do not move the only version.
5. Copy the source media as a separate folder. Preserve names and subfolders instead of scattering files across Downloads, Desktop and removable cards.
6. Export a reference MP4 and place a short text note beside it: project name, CapCut version, operating system, fonts and any paid/downloaded assets.
7. Test the copy before you reset or replace the computer.

Keep CapCut versions close when testing a copied desktop draft. Newer builds may migrate a project, and moving a migrated copy back to an older build can fail. For platform setup and update choices, use the current CapCut for PC guide or CapCut for Mac guide.

Manual folder copying is an advanced fallback, not a promise of cross-platform portability. Keep the untouched original. Never rename JSON files, merge two project folders or edit metadata as part of a routine transfer.

How to move a CapCut project to a new phone

On iPhone and Android, local projects normally live inside CapCut’s app-managed data. That makes manual project-folder transfer unreliable for ordinary users. The safer route is to upload the editable project to the intended Space, sign in on the new phone with the same method and open the project there.

1. On the old phone, open every important draft and resolve missing clips first.
2. Upload the project to the correct Space and keep the phone awake until the transfer finishes.
3. Preserve the original camera clips and downloaded audio outside CapCut as well. A cloud project does not excuse deleting the source library before testing.
4. Install CapCut on the new phone from the official store and use the same login method.
5. Open the project from Spaces, scrub the timeline and make a small harmless edit.
6. Close CapCut, reopen it and confirm the edit is still present.

Do not delete the old app just because the new phone shows a project card. Recent community reports still describe editors losing local work after a reinstall or device failure. Those reports are not proof that every phone behaves the same way, but they are a good reason to test the second editable copy first.

How to transfer a project to another editor

If another person needs the layers, captions and timing, send access to the project in a shared Space and confirm who has editing permission. CapCut’s current collaboration guide describes a hand-off model rather than unrestricted simultaneous editing: one editor can transfer editing permission to another member.

Before the hand-off, agree on four things:

• which Space and account own the project;
• who may edit and who only needs to review;
• where original media, fonts and licensed audio are stored;
• which export is the approved visual reference.

For review-only work, a rendered video or review link may be enough. For editing, it is not. If a teammate imports your MP4, they receive one flattened clip, not your timeline.

Why an exported MP4 is not a project backup

An MP4 preserves the picture and sound you rendered. It does not preserve separate text layers, keyframes, masks, cuts, captions, effects or audio tracks. CapCut’s official guide to importing a previous project into another edit is explicit: the exported video returns as a single clip, and its individual layers are no longer separately editable.

Still keep a reference export. It helps you spot a missing font, different caption wrap, broken effect or audio-sync shift after transfer. Think of it as a picture of the finished job, not the job’s source file.

Verify the transferred project

Run this check on the copy, not the original:

1. Open the full timeline. Confirm the duration and track count look right.
2. Jump to the beginning, middle and end. Look for red placeholders, silent audio, missing captions or substituted fonts.
3. Test device-dependent assets. Downloaded effects, templates, fonts and licensed music may need to be fetched again or may not be available under another account.
4. Make one reversible change. Move a text layer by one frame, close the project, reopen it and confirm the change saved.
5. Export the hardest section. Choose a part with captions, overlays, speed changes and layered audio. Watch the file on another player.
6. Keep the old copy. Retain it until you have completed real work on the destination device.

If clips are missing, reconnect them from the preserved source-media folder. Do not delete empty placeholders or rebuild the timeline until you have backed up both the original and transferred project folders.

Backup mistakes that lose CapCut projects

• Trusting autosave. Autosave can update the only local copy; it does not create an independent recovery point.
• Signing in with the wrong method. The email may look identical while CapCut opens a different account.
• Copying only the smallest draft folder. The timeline may still point to media stored elsewhere.
• Moving instead of copying. One failed transfer can leave you with no known-good original.
• Copying while CapCut is open. Metadata can change during the copy.
• Counting an MP4 as editable backup. It cannot restore separate layers.
• Deleting the old device too early. A thumbnail on the new device is not a tested project.

Frequently asked questions

Does CapCut automatically back up projects?

CapCut autosaves edits, and signed-in projects may use cloud features, but autosave is not the same as a verified backup. Check that the project appears in the intended Space and opens as an editable timeline on another device.

Can I transfer a CapCut project from phone to PC?

Yes, the safest route is to upload the project to CapCut Spaces, then sign in on the PC with the same login method and open the project there. Test captions, effects and source media before deleting the phone copy.

Can I transfer a CapCut project without exporting it?

Yes. Use Spaces for cross-device access or preserve the complete local project folder on Desktop. Exporting creates a finished video, not a portable editable timeline.

Can I copy a CapCut project folder to another computer?

You can make a desktop backup by copying the complete project folder while CapCut is closed, but treat it as an advanced fallback. Preserve source media, keep the original untouched and test the copy with a compatible CapCut version.

Why is my CapCut project empty on the new device?

First check the login method and Space. Google, email, TikTok and Facebook sign-ins can point to different accounts. If the timeline opens with blank clips, reconnect the preserved source media rather than deleting placeholders.

Is CapCut cloud storage enough for a long-term archive?

Do not rely on one service as the only archive. Keep the editable project, source media and reference export in a second location you control, then test that copy periodically.