CapCut is the quick-edit king on phones, and the Windows version promises the same speed on your Copilot+ laptop — until the preview goes black, an export dies at 97 percent, or the app simply vanishes mid-edit. The features are all there; the ARM execution is where it wobbles.

Most CapCut problems on Snapdragon and Ryzen AI laptops come down to hardware acceleration assumptions: the app expects an Intel/NVIDIA media pipeline, and when the ARM driver answers differently, previews break, encoders stall, and effects crash the render thread. Add a cache that balloons on small SSDs and you have the full picture.

This guide gives you six fixes in order: pick the right build, fix the GPU and preview path, stabilize exports, clear cache and storage pressure, handle effects and templates, and finish with a clean reinstall.

Why this happens

  • Hardware acceleration built for Intel/NVIDIA: CapCut’s GPU decoding, preview rendering, and hardware export encoding assume a driver stack that ARM graphics drivers only partially implement — the mismatch shows up as black previews and failed exports.
  • Two different Windows builds: The Microsoft Store version and the direct-download desktop version of CapCut differ in packaging and update cadence; on ARM, one is frequently more stable than the other and users rarely try both.
  • Cache and temp files filling small SSDs: CapCut caches aggressively — proxies, thumbnails, draft renders. On a 256 GB Copilot+ drive this fills fast, and a full disk produces export failures that look like encoder bugs.
  • Effects and templates with x64-only components: Some effects, transitions, and downloaded templates bundle native code compiled only for Intel. They can crash the app the moment they hit the timeline.
  • Aggressive power management during exports: Modern Standby power behavior and battery-saver throttling can starve a long export of CPU time, producing stalls and timeouts on battery power.
  • Outdated app version: CapCut updates frequently and ARM fixes land quietly in patch notes. Running a months-old build means running months-old ARM bugs that are already fixed.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Update CapCut and try the other Windows build

CapCut ships fast and fixes ARM issues without fanfare. Before touching settings, make sure you are current — and if you are, try the other packaging of the app, because on ARM they genuinely behave differently.

  1. Open CapCut, go to settings, and check for updates — install whatever is pending and restart the app.
  2. Test your failing operation (preview, export) on the updated build before changing anything else.
  3. If problems persist, note which build you have: Microsoft Store or direct download from CapCut’s site.
  4. Install the other build alongside (or after uninstalling the first) and test the same operation — the Store build’s sandboxing and the desktop build’s bundled codecs fail in different ways on ARM.
  5. Keep the stable one and fully uninstall the other so they cannot fight over file associations and cache folders.
  6. Going forward, check for updates weekly while you are actively editing — CapCut’s ARM fixes arrive as ordinary updates with no announcement.

Fix 2: Fix the black preview and GPU rendering

A black preview with audio playing is the signature ARM issue, and it is almost always the GPU decode/render path. CapCut lets you step down to software rendering — slower, but it works.

  1. Open CapCut Settings > Performance (or the playback settings panel) and look for hardware acceleration / GPU rendering options.
  2. Disable GPU-accelerated preview and hardware decoding, switching to software rendering.
  3. Close and reopen the project — the preview should now show video instead of black.
  4. If software rendering fixes it, update the graphics driver from your OEM (Dell , HP , Lenovo ) — a current Adreno or Radeon driver restores some GPU features on ARM.
  5. After the driver update, re-enable GPU features one at a time and retest; keep whatever stays stable and leave the rest on software.
  6. For timeline stutter even with video visible, generate proxy media for 4K clips — proxies sidestep the decode problem entirely and make editing smooth on any chip.

Fix 3: Stabilize exports

Export failures — crashes, freezes at a fixed percentage, or corrupt output files — usually mean the hardware encoder choked. Prove it by exporting in software, then work back toward hardware encoding.

  1. In the export dialog, switch the encoder from hardware to software encoding (sometimes labeled “CPU encoding”).
  2. Lower the export resolution one step (4K → 1080p) and the bitrate modestly for this test export.
  3. Run the export — if it completes in software, the hardware encoder path was the failure.
  4. Update the graphics driver (Fix 2, step 4) and retry hardware encoding; on a current driver it often works for H.264 even when it failed before.
  5. If hardware encoding still fails, keep software encoding for final exports — it is slower but reliable, and an overnight render beats a crashed one.
  6. Always export on AC power with the Windows power mode set to Best performance — battery-saver throttling mid-export is a classic cause of the “stuck at 97%” freeze.

Fix 4: Clear cache and free disk space

CapCut’s cache grows silently until the drive chokes. When exports fail with vague errors or the app slows to a crawl, assume the cache first — it is the cheapest fix on this list.

  1. In CapCut settings, find the cache management option and clear the preview/proxy cache.
  2. Check free space on your system drive — keep at least 20–30 GB free; video editing below that threshold invites failures.
  3. Move the cache location to a larger secondary drive if you have one, in CapCut’s settings.
  4. Delete old projects and drafts you no longer need — CapCut keeps project media cached even for projects you have not opened in months.
  5. Empty the Windows Temp folder and run Disk Cleanup on the system drive for good measure.
  6. Retest the failing export — cache-related failures typically vanish immediately after this cleanup.

Fix 5: Isolate crashing effects, transitions, and templates

When one specific effect or template crashes the app every time, the asset — not CapCut — is broken on ARM. Find it by removing recent additions.

  1. Duplicate the project so the original is safe, then in the copy remove the most recently added effects, transitions, or downloaded templates.
  2. Test preview and export after each removal until stability returns — the last removed item is the culprit.
  3. Re-download the offending template or effect fresh; corrupted downloads are common and a clean copy sometimes works fine.
  4. If the fresh copy still crashes, replace it with a built-in alternative — third-party effect packs are the most likely to contain Intel-only native code.
  5. For text effects and auto-captions that misbehave, check CapCut’s language pack downloads are complete — partial downloads produce crashes that look like rendering bugs.
  6. Note that CapCut’s AI features (background removal, auto-reframe) are the heaviest users of the very GPU paths that struggle on ARM — if they crash, do that step on the phone app and import the result.

Fix 6: Clean-reinstall CapCut

When the app crashes on launch, on a blank project, or after every fix above, the installation is corrupt — possibly a Store/desktop hybrid mess. Wipe it properly.

  1. Uninstall CapCut completely (Settings > Apps), choosing the full uninstall that removes user data if offered.
  2. Manually check AppData\Local and AppData\Roaming for leftover CapCut folders and delete them.
  3. Restart the laptop — CapCut leaves background processes that a plain uninstall does not kill.
  4. Install fresh from the other source than the one that failed (Store vs. direct download, per Fix 1). Note there is no Linux build of CapCut — if you dual-boot Linux on your Snapdragon laptop , keep Windows around for editing.
  5. Sign in, but do not restore old settings or sync old drafts yet — test a new blank project first.
  6. If the blank project works, reintroduce your media and effects gradually. For context on how ARM64-native versus emulated apps differ on this platform, the ARM64EC explainer is worth a read — it clarifies why some apps behave and others do not.

Closing

CapCut on an ARM laptop is a settings problem, not a lost cause: run the current build (try both packagings), step GPU features down to software where the driver cannot cope, keep the cache and disk clear, and quarantine Intel-only effects. Do the fixes in order and the quick edits stay quick.

Frequently asked questions

Does CapCut work on ARM Windows laptops?
Yes, CapCut installs and runs on Windows 11 on ARM, but it was built with Intel and NVIDIA machines in mind. Common issues include black previews, export failures, and crashes during effects-heavy edits — most are fixable with the settings below.
Why is my CapCut preview black but audio plays?
A black preview with working audio almost always means GPU-accelerated decoding or rendering failed on the ARM graphics driver. Switch CapCut to software rendering, update the OEM graphics driver, and retest.
Why does CapCut fail when exporting video?
Export failures usually come from hardware encoding hitting an unsupported driver path, a full or corrupted cache, or an effect the ARM build cannot process. Export with software encoding at a lower resolution first to isolate the cause.
Should I use the Microsoft Store or desktop version of CapCut?
Try both. The Microsoft Store build and the direct-download desktop build are packaged differently, and on ARM machines one often behaves noticeably better than the other. Keep whichever is stable and uninstall the other.