“No internet connection” in CapCut doesn't always mean your internet is down. CapCut may fail to reach templates, sign-in, cloud sync, AI, account checks or export while other sites still load.
Before you change anything, check how far the problem reaches. Try another app, another network and, if possible, another device. That tells you whether to fix CapCut, the device or the router, or to wait out a wider service problem.
Quick answer: save your work, then test another app and a trusted network. Before you sign out, update or reset anything, verify an independent project backup and its source files. A local save or a duplicate on the same device doesn't count as that backup. If you can't verify a usable copy, keep the working session open. Once your work is protected, restart CapCut, check mobile-data access and, if needed, sign in with the original login method. On Web, try a private window. Leave system App Data and the installer alone until every unsynced project is safe.
This page explains connection checks rather than reporting a live outage.
What You Can Still Do Offline
On Mobile and Desktop, basic timeline work may continue with media and assets already stored locally. That's not a promise that every project exports offline. If a project contains cloud media, online templates, AI output, or account-checked or paid assets, it may need a connection before it renders correctly.
CapCut Web depends on the browser and a cloud session, so it needs a live connection. Cloud sync, new asset downloads, templates, music catalogs, AI features and sign-in lean on online services too. CapCut's official no-internet guide lists templates, sync and AI access among the common symptoms.
Test the exact workflow you care about. Open the project, play a section with the affected assets and render a short sample. That result tells you more than any broad “CapCut works offline” claim.
Find Which Connection Is Failing
- Test another app or site. If nothing connects, fix the device or network first.
- Switch networks. Try cellular/mobile data instead of Wi-Fi, or a trusted hotspot instead of the current network.
- Test another device. The same CapCut failure across devices points toward the network, account or service.
- Save local work. Verify the independent backup described above before sign-out, reset or update steps. Do not treat a same-device duplicate as protection against app-data loss.
- Restart and retry. Fully close CapCut, reopen it, then refresh the account session only if needed and your backup is verified.
Public, school and workplace networks can block media, cloud or authentication endpoints while regular browsing still works. A captive portal can also leave the device “connected” to Wi-Fi without full internet access. Open a normal browser page and finish any network sign-in before you blame the editor.
Is CapCut Down, or Is the Failure Local?
One error banner doesn't tell you much, so look for a pattern. When Mobile, Desktop and Web all fail on different networks and other users report the same functions failing at the same time, a service incident gets more likely. If only one device fails, start with its permissions, account session and security rules.
Multiple devices, networks and matching recent reports strengthen the case for an outage, but they aren't prerequisites. An official acknowledgement of the affected function can be enough reason to stop local resets, and a regional or account-specific incident may have few public reports. Crowdsourced trackers help as extra signals, but they don't prove that every CapCut service is healthy. If the cause is still unclear, use CapCut’s official problem-report form.
Once the evidence points to an outage, stop changing local settings. Save the project, note the time and the exact function that fails, and retry later. With a clean record, you can tell a service recovery apart from a random local change.
Read the Error Pattern Before Choosing a Fix
CapCut can show the same network-style warning for failures in different parts of the product. Before you touch DNS, firewall or app data, write down what still works. A timeline that plays while Templates fails is a different problem from every CapCut app failing to sign in.
| What fails | What still works | Start here |
|---|---|---|
| Only CapCut Web | Desktop/Mobile and normal sites | Private window, extensions, cookies/site data and another browser |
| Templates, effects or AI only | Local timeline and imported media | Account, catalog availability, network filtering and service status |
| Pro or paid assets | Free tools and ordinary connection | Login method, purchase account and entitlement refresh |
| Export only | Editing and preview | Short-range test, cloud/paid assets, storage, hardware and project complexity |
| Every platform on several devices | Other online services | CapCut service, shared network filtering or account-level failure |
If the app opens but the preview stays black, test the media and a short render before you call it a connection fault. The CapCut black-screen guide covers preview and source-file causes. For broad symptom triage, start with CapCut Not Working, or head back to the CapCut Fixes hub to pick another focused route.
A failed install or update download happens at a different stage than an editor session that loses cloud access. CapCut's download and installation checklist covers network, storage and device-support causes. If the official installer times out, that still isn't a reason to use an unverified download.
If Pro features disappear, CapCut's entitlement help page stresses differences in platform, account and purchase method. Restore the right session before you buy again. For failures that only hit export, check the exact project against CapCut's platform-specific export checklist. Web connection trouble, Desktop resources and Mobile limits don't share one fix.
I'd change only one variable at a time. Switch network, account, app version and security settings together, and a successful retry won't show which condition mattered. A failed retry can leave several new problems behind.
Fix It on iPhone or Android
- Open a browser or streaming app to confirm the phone has usable internet.
- Switch between Wi-Fi and cellular data.
- Check that Airplane Mode is off and CapCut is allowed to use mobile data.
- Fully close CapCut from recent apps and reopen it.
- Restart the phone if the error survives the app restart.
- Save, then use CapCut's own Clear Cache control if available.
- Update CapCut from the Apple App Store or Google Play.
- Sign out and back in only after local work is protected.
On iPhone, open Settings → Cellular (called Mobile Service or Mobile Data in some regions), find CapCut and check its app switch. Apple's mobile-data instructions cover the per-app control and possible carrier charges. If you're on a limited or roaming plan, skip large uploads while you test.
If background uploads are the problem, compare Low Data Mode on the connection you're using. Apple's Low Data Mode paths are Settings → Cellular → Cellular Data Options for LTE/4G, with an extra Data Mode step for 5G, or Settings → Wi-Fi → the information button beside the network. Dual-SIM layouts can put the control under the selected number. Note the original setting, test briefly and restore it afterward, even if the test works. Low Data Mode limits background activity; it doesn't prove why an active foreground request failed.
On a Pixel, if a background task gets interrupted while Data Saver is on, use Settings → Network & internet → Data Saver → Unrestricted data → CapCut. Google's Data Saver guidance says apps that are currently active can still use mobile data. The setting is a background-data exception, not a universal internet switch. Other Android manufacturers use different menus. Restore the original exception after you test, and keep the data cost in mind.
Don't clear system App Data. CapCut explicitly warns that doing so permanently deletes local projects. A cache is replaceable temporary material; app data can include the project state you're trying to save.
If the error started after a crash and nothing changed on the network side, secure the project and work through the CapCut crashing guide. Keep storage repair and network troubleshooting apart until you know which symptom came first.
Fix It on Windows or Mac
- Test websites and another online app on the same computer.
- Restart CapCut, then restart the computer.
- Close unused heavy apps and confirm that the drive has working space for CapCut's temporary files.
- Verify the independent project backup before refreshing the CapCut account session.
- Update CapCut through its update control or official installer.
- Check firewall or endpoint-security logs for a block matching the official CapCut app, destination and failure time. Do not add a rule merely because a network banner appears.
- Test a trusted hotspot to separate computer settings from the home or office network.
Leave the firewall and antivirus on. When CapCut contacts a server, that's an outbound request, so adding an incoming exception isn't a general fix. Microsoft's Windows Firewall rules guidance recommends allowing outbound traffic by default for most deployments, though explicit block rules can override allow rules. Find the specific block instead of opening ports or switching on both network profiles across the board.
Apple's built-in Mac firewall controls unwanted incoming connections. Third-party endpoint tools or network filters can add their own restrictions. If you've confirmed a block that explains the failure, ask the administrator or security-tool vendor for the narrowest fix that fits. Never bypass work or school policy.
If paid tools vanish after the connection comes back, use the CapCut Pro not-working guide to confirm you're on the same login method and subscription account. At the export screen, a network error and an account mismatch can look alike.
Fix It in CapCut Web
- Save and let uploads finish before reloading the tab.
- Open CapCut Web in a private/incognito window.
- Compare the same failing action. If private mode works, test nonessential normal-window extensions one at a time, restoring each after the test.
- If Chrome reports blocked third-party cookies during sign-in, consider a temporary exception for that site only, provided your device policy permits it. Remove the exception after testing.
- Test another current browser.
- Try another trusted network. Preserve the working session and verify the project backup before signing out or removing site data.
A content blocker, privacy extension or stale site session can interfere with authentication or media requests while ordinary sites load fine. Chrome blocks third-party cookies by default in Incognito, and extensions explicitly allowed in Incognito can still run. So if CapCut Web still fails in Incognito, browser state isn't ruled out; if it works, that doesn't prove the cache alone was to blame.
If the browser flags blocked cookies, Chrome's site-specific cookie controls give you a narrower test than allowing cookies everywhere. An Incognito exception lasts for that private session, but remove any regular-window exception after testing. Keep required privacy and managed extensions on. Remove just the CapCut-specific site data, and only after you've confirmed the saved project opens elsewhere and its source media is safe. If you can't verify that, keep the original tab and contact support instead.
CapCut's guide says Web needs a stable connection and cites 5 Mbps as a baseline. Speed alone won't rule out high latency, packet loss, DNS trouble or endpoint filtering. Keep your original media outside the browser, and for upload or browser-specific failures, work through the full browser connection workflow.
Match the Fix to the Failing Feature
Templates, effects, fonts or music won't load
Those catalogs are dynamic and often streamed, so check another category, account and platform. Your existing local edits may keep working while new materials fail. Our overviews of CapCut effects and CapCut templates explain how catalogs differ across platforms.
Auto captions, AI voice or text to speech fails
Online processing or account credits may be involved, so confirm the connection and account before you regenerate anything. For feature-specific checks, see the auto-captions guide, AI voice guide or text-to-speech guide.
Cloud project won't sync
Treat the newest cloud copy as unverified until it opens correctly. Don't touch the device that holds the latest local edit, confirm the account and available cloud space, and don't sign out everywhere until you've documented the project state.
Export asks for internet or fails
Test a short section that contains any cloud, template, AI or paid assets with the selected-range export or duplicate-project workflow. Web exports need a connection; on Desktop, failures can also come from hardware, storage or project complexity. If the connection works but the render stalls, switch to the CapCut export-stuck guide.
Router and Restricted-Network Checks
Only restart the router after you've saved active work and confirmed that other devices in the house are affected too. Give it time to reconnect fully. If CapCut works on a hotspot but not on home Wi-Fi, look at parental controls, DNS filters, ad blocking, router security and ISP conditions.
Don't bypass managed network controls or a VPN you need for privacy or safe access. Ask the administrator or provider to look into it instead. On a device and connection you control, write down the current VPN, proxy, DNS-filter or ad-blocking setting before you consider one brief comparison. Restore the protection immediately afterward, whether the test works or not. If disabling a filter changes the result, that's evidence to look into a narrow rule with its provider, not a reason to leave protection off permanently. Don't copy random public-DNS or VPN settings, and don't use this process to evade regional or organizational restrictions.
On a managed network, give the administrator the exact time, device, CapCut version, failing feature and error text. “The internet works” is less useful than “sign-in and templates fail on two devices, but ordinary HTTPS sites load.”
Reinstall Only After Local Projects Are Safe
Reinstalling comes last, not first. Before you do it, confirm that the problem is limited to one app installation, that updating didn't help, and that every unsynced project has a usable backup or verified cloud copy. CapCut's connection checklist warns against uninstalling during an update because unsynced local projects can be lost.
Before you remove the app, write down the original login method, app version and local project locations. Stick to the official App Store, Google Play or CapCut installer. An unofficial downgrade can add security risk and may not open newer projects correctly. Our CapCut for PC walkthrough and the CapCut Android download steps cover the official routes.
If You Have a Deadline
Duplicate the project before you simplify it. Leave the original intact, then make a recovery copy and swap only the online asset that's blocking progress for a local, rights-cleared alternative. A locked template may not let you replace its internal assets. If it won't, use another permitted template or build a clean copy from your own source clips instead of dismantling the only editable version. Test a short export after each replacement.
If Desktop can still use imported media, finish the essential cuts locally and hold off on cloud sync, new templates and AI steps. When Web holds the only copy, avoid repeated reloads until you've confirmed saves and uploads. Tell the client what failed, what's still preserved, and whether the limitation affects the final render or only an optional connected feature.
What to Send CapCut Support
- Device model and operating-system version.
- CapCut platform and exact app/browser version.
- Account login method, without sending a password.
- Exact error text and the function that fails.
- When it began and whether another network/device works.
- A screenshot or short screen recording with private data removed.
- Whether local editing, sign-in, sync and short test export work separately.
Send it through CapCut’s official support form. If support asks for identifiers, its UID/DID instructions show where to find them. Share those only with verified support, and keep them out of public screenshots. A report like that helps support tell authentication, catalog, project, rendering and network failures apart. While you wait, keep the latest local copy safe and don't repeat destructive resets.
CapCut Connection FAQ
Why does CapCut say no internet when my Wi-Fi works?
CapCut can fail while other sites work because of an expired session, blocked app permission, browser extension, filtered network, service outage, account check, or a problem reaching one CapCut service. Test another network and another device to narrow the scope.
Can CapCut work without internet?
Some editing with already imported local media may work in the Desktop or Mobile app, depending on the project. Web, cloud sync, new templates and assets, AI services, and some account or paid-asset checks need or may need a connection.
Will clearing CapCut cache delete my projects?
Use only CapCut's own Clear Cache control after saving. Avoid system App Data or Storage data: CapCut warns that clearing it can permanently delete local projects.
Should I reinstall CapCut to fix a network error?
Not first. Test the scope and protect unsynced work with a verified independent backup before sign-out, updates or resets. Restart and check the relevant network setting first. Keep a working session if you cannot verify the backup. Reinstall only after safer checks fail and local projects and source files are recoverable.
Why do CapCut templates or effects say no internet?
Many templates, effects, fonts, music items and AI features are downloaded or checked online. A local timeline can remain editable while those catalogs fail. Test account status, another network and whether the same catalog fails on another device.
Why does CapCut Web keep losing connection?
Web depends on a live browser session. Preserve the saved project and original media, then compare another browser or a private window. Chrome Incognito blocks third-party cookies by default and can run explicitly allowed extensions, so either result needs interpretation. Test only permitted site-specific exceptions and restore them afterward. Do not clear site data or sign out until your work is recoverable.
Can a CapCut outage block export?
It can affect Web exports and projects that need cloud, account, AI, template, or paid-asset checks. A basic local Desktop export may still work. Export a short test from the exact project instead of assuming one rule fits every project.
For a different error, return to the CapCut Fixes hub and choose the symptom that matches. When the service is reachable again, test one cloud feature and one short export before resuming a long edit.