Inside an open CapCut project, a black screen usually falls into one of three categories, and each needs a different fix. The preview window can go dark while your project is intact. The export can come back as audio over black even though the preview looked correct. Or the finished file can play black in one app and fine in another.
Before changing any setting, export five to 10 seconds of the affected part of your timeline. CapCut recommends this test on its own preview mismatch page, and it splits the problem in half. If the short export plays correctly, that section of the edit is likely intact, and the preview path becomes the main suspect. If it comes back black, look at the media, the timeline or the encoder instead.
Before you change anything: duplicate the project before removing or disabling timeline elements. Before clearing app data or reinstalling CapCut, upload the project to CapCut Space and confirm the cloud copy opens. A local duplicate does not protect you against uninstalling the app, which CapCut warns on its own template troubleshooting page can take local drafts and unfinished projects with it.
| What you see | Likely area | First thing to try |
|---|---|---|
| Preview black, timeline thumbnails look normal | GPU decoding or render cache | Clear the render cache, then test the decoding setting your version exposes |
| Whole app window or interface is black | Application or display layer, not the project | See CapCut not working for app-level failures |
| Preview black on mobile right after importing | Thumbnail generation, permissions or file size | Wait for thumbnails, import fewer files, then check photo permissions |
| Export plays audio over black | Timeline, source decoding, encoding or playback | Isolate with short section exports from a duplicated project |
| Black only at the end of the export | Trailing clip or a track running past the video | Delete the trailing element, then check caption and overlay tracks |
| Only screen recordings turn black | Variable frame rate or an unsupported encoding | Make a constant frame rate H.264 copy and import that |
| Project or template turns black after moving devices | Missing or unlinked media | Relink the media, and finish template edits on the platform they were built for |
| Black bars down the sides | Canvas ratio does not match the footage | Change the aspect ratio or scale the clip to fill |
| Exported file black in one player only | Playback compatibility on that device | Test in VLC and a second player before blaming the export |
| Checked for this guide | |
|---|---|
| Last checked | July 28, 2026 |
| App builds | CapCut mobile 18.7.x (iOS / Android), desktop 18.8.x — the current public builds at the check date |
| Devices | iPhone 17 Pro, Pixel 10, M4 MacBook Air, Windows 11 desktop |
| Region and plan | US store listings, free account unless a section says otherwise. Features, limits and prices vary by region and change without notice. |
How guides are tested is described on the author page. Spotted something outdated? Tell us and we'll re-check it.
Why CapCut's Own Advice on Black Screens Contradicts Itself
The setting almost everyone reaches for first is hardware acceleration, and CapCut's help center points in both directions at once.
Its page on video not showing in CapCut, updated March 25, 2026, tells PC users to update graphics drivers and enable hardware acceleration. Its page on exports stuck at 1%, updated a week earlier, tells PC users to open Settings, then Performance, and disable hardware encoding. Seven days apart, pointing at the same Performance tab from opposite directions.
Neither page is wrong. Hardware-accelerated decoding draws frames into the preview window. Hardware-accelerated encoding writes the finished file. Recent desktop versions may expose these as separate controls, alongside an interface-rendering option, which is why one label in a help article can send you to the wrong switch.
A workable approach: for a black preview, update the GPU driver first, then test whichever decoding or interface-rendering option your version exposes. For a black or stalled export, test with hardware encoding disabled. Both are diagnostic tests, not a permanently correct configuration.
One more page worth knowing about. CapCut's article on black screens while importing names hardware acceleration as a likely desktop cause, then lists steps that never touch it. If you followed those and nothing changed, you did not miss anything.
CapCut Black Screen in the Desktop Preview Window
Work through these on Windows or macOS, restarting CapCut after each change, since most of these settings take effect on relaunch.
- Clear the render cache. Settings, Draft tab, trash icon next to Cache Size. Corrupted cache is a common cause CapCut itself lists for preview and export problems.
- Check the clip, not the app. Select the clip and look at opacity and visibility. A clip at zero opacity or toggled off still plays its audio, which is why this gets mistaken for a rendering fault.
- Turn proxy editing off. Proxy mode swaps in low-resolution copies for smoother playback, and CapCut notes it can misrepresent scaling and blur. In CapCut's current desktop instructions, Proxy is under Menu → Settings → Performance. Its location may differ slightly between builds.
- Update your graphics driver. On Windows, use the NVIDIA, AMD or Intel utility rather than Windows Update. On macOS, run System Settings, then Software Update.
- Test the acceleration options. Menu, Settings, Performance. Some builds expose separate decoding and encoding toggles; some older ones carry an option called Render interface with GPU, which affects the preview rather than the export encoder. Change one at a time so you know which one did the work.
To separate a graphics problem from a project problem, create a new project and drop in a known-good H.264/AVC MP4 recorded on a different device. If that renders black too, a GPU driver or application rendering path becomes the more likely area. If it plays, the fault sits in your original project or its media. Install-side checks are covered in the CapCut for PC guide.
CapCut Black Screen on iPhone and Android
If every item in the album picker is black, start with the import path rather than the editor. Give the app time to generate thumbnails, import a smaller batch instead of everything at once, and check whether the files are unusually large. CapCut lists refreshing the media view and restarting the app ahead of anything more involved.
Check permissions. Open your phone settings, find CapCut, and confirm photo and media access is granted. A partial grant on iOS, where you selected only some photos, leaves everything you left out unavailable to the app.
Re-import the clip. Tap New video and bring the file in again.
Clear the cache, not the data. On Android, Settings, Apps, CapCut, Clear Cache. Google documents Clear storage as permanently deleting all app data, so leave that button alone. On iOS, Apple documents Offload App as removing the app while keeping its documents and data, though CapCut still ties draft safety to cloud sync. Upload anything you care about to CapCut Space before either operation.
Check the playhead. If it sits past the end of your last clip, the preview is showing empty timeline, which renders black.
Expect proxy differences. CapCut states that mobile previews use lower-resolution proxies, so image quality can differ from the export. Layout and timing should match. If they do not, export a short test: the cause may be a keyframe or timeline mistake, but rendering glitches, template problems and cache errors produce the same symptom.
4K or 60fps footage on a mid-range phone can produce black frames, frozen previews and failed exports under memory pressure, and an SD card adds to it. Move the media to internal storage, close background apps, and make sure the battery has enough charge before exporting.
If the phone is already hot, disconnect it from power and let it cool before trying again. Google tells Pixel owners to unplug an overheating phone and stop using it until it cools. Apple documents charging slowing or stopping and frame rates dropping once an iPhone passes its normal operating range. Charging a hot phone while it renders works against you.
CapCut Black Screen in the Web Editor
CapCut recommends reproducing editor problems in the latest Chrome, Edge or Safari on macOS. If a project renders in one of those but not in Firefox or Opera, treat browser compatibility as the likely cause. CapCut's own pages are not consistent about which browsers support every web feature, so a black preview in Firefox is worth testing rather than assuming.
Refresh the tab with Ctrl+R or Cmd+R, since browser editors hold a lot of state in JavaScript and it can desync. Check layer order and move your clip to the top layer if it has slipped underneath another element. A weak connection leaves placeholder frames unloaded, which look black rather than broken.
CapCut describes web rendering as cloud-assisted and a best-effort approximation rather than pixel-perfect output, and names heavy filters, nested overlays and long text animations as the elements that render least reliably in a browser. What the web version does and does not handle is covered in the CapCut web editor guide.
CapCut Exports a Black Screen With Audio Only
Audio over black confirms the audio stream survived. On its own it does not tell you whether the failure happened in the timeline, in source decoding, in video encoding or in playback. Work through those in order, in a duplicated project.
Isolate the material. Work only in a copy. Disable or remove suspect clips in that copy, then export short sections to find the material that fails. CapCut's export error code page points the same way. Errors 4114 and 10004 both ask you to export in smaller parts to locate the problem clip. Error 10006 asks you to relink imported media, and 22113 asks you to rebuild every compound clip in the draft. If you see a code, start there. If only the middle of the export turns black, test around the first black frame and inspect the transition, effect, compound clip or source file immediately before it.
Check the encoder. Open Settings, then Performance, and test an export with hardware encoding disabled. Disabling hardware encoding may make CapCut fall back to software encoding on the CPU, which can make the export slower. If that changes the result, you have located the problem rather than solved it.
Test a different export codec. A user documented one version of this on Intel's support forum in August 2025, running CapCut 6.9.0 on an Arc B580. AV1 exports fell back to 100% CPU with the GPU encoder idle. H.264 exports from the same project used the GPU normally. Intel could not reproduce it, and the reporter later confirmed a clean driver reinstall of version 32.0.101.7028 resolved it, after which the thread was closed. Treat this as one case on one version, not as evidence that AV1 is broken. H.264/AVC is a useful compatibility test, not a guaranteed fix.
Check AI features one at a time. If only clips using Super Resolution or Enhance Quality turn black, duplicate the project and disable that feature on a single test clip. Do not delete files from CapCut's internal folders to force a re-render, since that risks the rest of the draft.
Lower the resolution, frame rate or bitrate too, and confirm you have several gigabytes of free disk space for temporary files. Export settings are covered in more depth in the CapCut export settings guide, and exports that stall rather than go black in the guide to CapCut exports getting stuck.
Black Screen at the Start or End of a CapCut Export
A dark tail is often not a rendering fault at all.
Some mobile versions and templates add a CapCut-branded ending clip. Delete the final clip if it appears. If your version still exposes Add Default Ending in Settings, switch it off for future projects.
Check whether anything runs past your last video clip. A caption track from auto-captions, a text layer, a sticker or an overlay extending beyond the final frame leaves CapCut rendering a black background underneath it for the difference. Zoom out until every track is visible and trim whatever overhangs.
Gaps in the timeline render as black frames too. Confirm your first clip starts at zero with no space in front of it, and that trimming has not left gaps between clips. Then check the tracks above your video for a stray overlay or transition layer with nothing visible in it.
Black bars down the sides or across the top are a different problem. That is a canvas ratio mismatch, usually 16:9 footage on a 9:16 canvas. Change the project ratio or scale the clip to fill the frame.
When a CapCut Black Screen Points at the Source File
Test the original clip in VLC and a second independent player. If the source is black or corrupted in both, the file itself becomes the likely cause.
Extension and format are not the same thing, and this is where most format advice goes wrong. MP4, MKV and MOV are containers. H.264/AVC, HEVC and AV1 are codecs that sit inside them. CapCut makes the point on its own import troubleshooting page: a file labeled MP4 may not be in a format CapCut recognizes, and renaming an extension changes nothing.
That page also states that supported formats vary by device, operating system and CapCut version, so check it against the version you are running rather than against a format list in someone's blog post.
What causes trouble is more specific than a file extension: an unusual codec profile, 10-bit or HDR footage, variable frame rate, a damaged file, or a hardware decoder that cannot handle the stream. A transcode to H.264/AVC with AAC audio in an MP4 at a constant frame rate is a compatibility test that standardizes several of those compatibility variables at once. Keep the original file, since transcoding can change HDR, color and image quality, and it will not repair damaged frames.
Screen recordings and game captures are common sources of variable frame rate footage. Make a constant frame rate H.264 copy and import that copy into a duplicated project rather than converting in place.
If media was moved, renamed or deleted after import, CapCut still points at the old path and shows black. Editing from an SD card, a USB drive or a synced cloud folder such as OneDrive or iCloud Drive can cause the same thing when the drive is disconnected or the cloud file is switched to online-only. Copy everything to internal storage first.
If the exported file plays in VLC but not elsewhere, that points at codec, HDR, color management or playback compatibility on the second device rather than a failed export.
CapCut Black Screen After Moving a Project or Template
Moving a project between devices is its own cluster of black-screen reports, and the causes differ from everything above.
If a project turns black after moving devices, confirm you used the same CapCut account and that the upload to CapCut Space finished before you opened the project elsewhere. If CapCut marks individual clips as missing or unavailable, relink those media files and re-export.
Templates behave differently again. CapCut states on its template preview page that a mobile or web template opened on CapCut Desktop can show only a single default frame, and that unfilled placeholders produce the same result. CapCut says the export still plays correctly if the project was completed on mobile first, and recommends building template edits on mobile rather than on desktop.
CapCut Black Screen Questions People Still Ask
Does a black screen mean I have lost my project?
Usually not. First confirm the timeline, the clip references and the original media files are all still present. Preview rendering runs separately from the project file, so a dark window on its own says little. Black clips after files were moved or deleted are a different situation, and that one needs the media relinked.
Why does CapCut export black video with audio only?
Audio over black confirms the audio stream survived, but it does not tell you where the video failed — timeline, source decoding, video encoding or playback. Work in a duplicated project, disable or remove suspect clips, then export short sections until the problem material shows itself. CapCut's own export error codes point the same way and ask you to export in smaller parts.
Why is only the start or end of my CapCut export black?
A dark tail is usually not a rendering fault. Some mobile versions and templates add a CapCut-branded ending clip, so delete the final clip if one appears, and switch off Add Default Ending where your version still exposes it. Also check whether a caption track, text layer, sticker or overlay runs past your last video clip — CapCut renders black underneath it for the difference.
Why is the CapCut preview black in Firefox but fine in Chrome?
Treat it as browser compatibility. CapCut recommends reproducing web editor problems in the latest Chrome, Edge or Safari on macOS, and its own pages are not consistent about which browsers support every web feature. If a project renders in one of the recommended browsers but not in Firefox or Opera, test there before assuming the project is damaged.
Why did my CapCut project turn black after moving devices?
Moving a project has its own set of causes. Confirm you used the same CapCut account on both devices and that the upload to CapCut Space finished before you opened the project elsewhere. If CapCut marks individual clips as missing or unavailable, relink those media files and export again.
Should I reinstall CapCut?
Treat it as a last step. Before you do: duplicate the project, upload it to CapCut Space, confirm the cloud copy opens, and keep your original source media somewhere safe. CapCut warns that uninstalling can cost you local drafts and unfinished projects.
Does turning off hardware acceleration slow CapCut down?
It can. Disabling hardware encoding may make CapCut fall back to software encoding on the CPU, which can make exports slower. Keep the switches separate: encoding affects the export, while decoding and interface rendering mostly affect the preview. Turn whichever one you changed back on once you know whether it made a difference.
If none of this resolves it, write down your CapCut version, operating system, GPU driver version and any export error code before contacting support. Those details decide whether anyone can reproduce what you are seeing.