ReelWorkshop imports your own filmed clips directly in the browser, up to 100 per project, and fingerprints and quality-scores each one as it comes in. When a clip won't import, the cause is usually the file itself, the browser tab's resources, or the connection carrying the upload, not a broken feature.
Most likely cause: file size or browser memory
Very large source files, especially long 4K clips straight off a camera or drone, can exceed what the browser tab can hold in memory alongside everything else already loaded in your project. This shows up as an import that appears to hang indefinitely or that drops silently partway through, rather than a specific error.
Second cause: an unstable connection mid-upload
If you're importing from cloud storage or a slow network, a dropped connection partway through the transfer will leave the import stuck rather than retrying automatically. Importing directly from a local drive or phone storage avoids this.
Third cause: too many tabs or background apps
Because encoding, preview and fingerprinting all run locally, other heavy tabs or apps competing for CPU and memory can starve the import process. This is more likely on laptops with limited RAM than on a desktop.
How to fix a stuck import
- Close other tabs and heavy apps
Free up memory before retrying, especially if you're on a laptop or have several browser windows open.
- Import in smaller batches
Add 10-20 clips at a time instead of all 100 at once, letting each batch finish fingerprinting before adding more.
- Move the file locally first
If the source is in cloud storage, download it to your device and import from there instead of importing directly from a cloud link.
- Refresh and reopen the project
ReelWorkshop saves your project as you go, so a refresh recovers your existing clips without losing prior work, then you can retry just the clip that failed.
Clicking import repeatedly while a previous attempt is still processing can queue duplicate attempts on the same file and make the tab less responsive, not more.
Preventing it next time
- Trim obviously unusable footage on your phone or camera before importing, so you're not carrying dead weight into the browser.
- Import in batches of 10-20 on lower-powered machines rather than dumping an entire folder at once.
- Keep source files on local storage during the import step, then archive them elsewhere afterward if you want.
- Check the current file size guidance in the app if you're working with long 4K clips, since practical limits depend on your device.
When it isn't a fixable import problem
If a specific file always fails on every device and every browser, it's more likely a format or corruption issue than a memory issue — see the pages on unsupported formats and corrupt files for the next step.