A failed compression does not always mean the video is unusable. Start with the stage that failed: upload, processing, or download/playback. The fix is different for each one.
| What you see | Most likely next step |
|---|---|
| Upload stops before the job begins | Keep the tab open, check the connection and try the file again |
| A pasted link cannot be fetched | Download the video first, then upload the local file |
| The encoder says the source is unreadable | Re-export the source from a player or editor |
| The format or track is unsupported | Convert the source to MP4, then retry |
| The job is queued or progressing slowly | Wait; long, 4K and H.265 jobs take longer |
| The result misses a hard upload cap | Use a target a few percent below the platform limit |
| The download link expired | Recompress the source; expired result files are deleted |
| Credits were reserved for a failed job | No action is needed; failed processing is refunded automatically |
The upload failed before compression started
An upload must finish before the cloud job can start. Until that point, closing the tab or losing the network connection can interrupt the transfer.
Check these in order:
- Compare the file with your plan limit. Signed-out visitors can upload up to 500 MB, free accounts up to 1 GB, and paid plans up to 1.5 GB. A payment cannot make a file above the current 1.5 GB service ceiling processable.
- Keep the tab open until the upload finishes. Once the cloud job has started, the tab can close and encoding will continue.
- Retry on a stable connection. Network speed affects upload and download time, even though it does not make the server encode faster.
- Use the file rather than a share page. A URL input must point directly to a publicly reachable video file. A Dropbox, Drive or other share page can block the fetch even when it opens in your browser.
If a URL import fails twice, download the source to your device and upload that copy. This separates a link-permission problem from a video problem.
The job is queued, stuck or taking longer than expected
A static progress number does not by itself mean the job has failed. Upload, queueing, encoding and exporting are separate stages, and only the encode stage changes the video.
Duration, resolution, codec and encoder settings matter more than the filename or container size. A long 4K file has many more frames and pixels to process than a short 720p clip. H.265 is also slower than H.264; in VidSmaller's measured billing data, it took about 3.8 times as much encoder time for the same kind of job.
After the upload is complete and the job has started, cloud encoding continues if you close the tab. Signed-in users can return through their history. Do not submit the same job repeatedly just because progress pauses for a short period; that can create separate jobs rather than speed up the first one.
The encoder rejected the source
VidSmaller turns provider errors into a small set of actionable messages. Use the message shown with the failed job:
- Source unreadable: the container index may be damaged or incomplete. This often happens when a recording was interrupted or a download ended early. Open the video in a player or editor and export a fresh copy, then upload the copy.
- Source unreachable: the cloud service could not fetch a URL. Confirm that the link is public and points to the file itself, or upload the file instead.
- Unsupported input: the container can be opened, but it includes a codec, track or DRM protection the encoder cannot process. Export an unprotected MP4 copy and retry.
- Processing capacity: nothing is wrong with the file. Wait a few hours and retry.
- Unknown processing failure: retry once. If the same file fails twice while other files work, re-export that source before trying again.
Renaming an extension does not convert a video. Changing clip.mkv to
clip.mp4 leaves the codecs and container data unchanged; use an actual export
or conversion when the source is unsupported.
The result is too large, too small or too blurry
A target size is a target, not a byte-for-byte guarantee. Video complexity, audio bitrate, container overhead and encoder behavior can move the final size slightly. If another service has a hard 25 MB ceiling, do not target exactly 25 MB. Leave a few percent of headroom or use one of VidSmaller's platform presets, which already includes a safety margin.
If the result is much too soft, the target may not contain enough bits for the video's duration and resolution. Use the video compression calculator to see the bitrate budget. Shorten the video, allow a larger file, or lower the resolution. Keeping 1080p at an extremely low bitrate usually looks worse than a clean 720p result.
If a compressed file is not meaningfully smaller—or becomes larger—the source may already be efficiently encoded. Avoid another generation unless you need a specific size, codec or compatibility change. For quality-targeted work, see why CRF does not predict file size.
The download is missing or expired
The download button appears only after the job reaches completed. If the job
is still queued or encoding, wait for the terminal status rather than starting
a duplicate.
Result links are intentionally temporary. Guest results remain downloadable for 2 hours; signed-in history keeps results for 7 days. When a link expires, the result file is deleted and cannot be restored from that URL. Recompress the original source to create a new result.
Download the result before leaving a guest session, and save it somewhere under your control if you need a permanent copy.
The downloaded video will not play, has no sound, or is out of sync
First try a current player such as the system's latest video app or VLC. If one player opens the result and another does not, the problem is usually playback compatibility rather than a damaged download.
For the broadest device support, retry with MP4 and H.264. H.265 can make camera footage smaller but is not supported by every older browser, phone or editor. If the source has no sound after compression, export the source as MP4 with a standard AAC audio track before uploading it again. The same re-export step often normalizes unusual timestamps that can produce audio/video sync problems.
If the newly downloaded file fails in every player, keep the original and the job details; do not overwrite the source with the result.
What happens to credits after failure?
A failed processing job is refunded automatically and in full, once per job.
Uploads and downloads do not consume credits; only billed encoder time does.
If the balance does not update after the job reaches failed, contact support
with the job ID rather than submitting the same source repeatedly.
What to include when contacting support
Send enough information to identify the stage without sending private video content in email:
- the job ID;
- the approximate time and time zone;
- the exact error shown on screen;
- whether the source was a file upload or URL;
- file extension, size, duration and resolution;
- browser and operating system;
- whether the same source failed twice and whether another video works.
That distinguishes an account or capacity issue from a damaged source much faster than “compression failed.”
FAQ
Why does my video upload keep failing?
The usual causes are a file above your plan limit, an interrupted connection, or closing the tab before upload completes. Check the size first, keep the tab open through the upload, and retry on a stable connection. For a pasted URL, use a public direct file link or upload the local file instead.
Can I close the browser while a video is compressing?
Yes, but only after the upload has completed and the cloud job has started. Closing the tab during upload can interrupt the transfer. Once processing has started, cloud encoding continues; sign in first if you want the job in your 7-day history.
Why is my compression job stuck?
It may still be queued, encoding or exporting. Long videos, 4K sources, H.265
and slower quality settings take longer. Wait before creating another job. If
the job reaches failed, follow the specific source, format or capacity message
shown with it.
Why did compression fail for one video but work for another?
The failed source may be incomplete, damaged, DRM-protected, or contain an unsupported track even if its extension looks normal. Re-export it as an unprotected MP4 and retry. Renaming the extension alone does not convert it.
Why is the compressed video larger than the target?
Encoded size can vary slightly because video complexity, audio and container overhead are not perfectly fixed. For a hard upload ceiling, target a few percent below the limit. If the difference is large, retry with target-size mode and a lower maximum resolution.
Why did the compressed file become larger than the original?
The original may already use an efficient codec or low bitrate. Re-encoding at a higher quality target can then add data instead of removing it. Keep the original unless you need a smaller explicit target or a compatibility change.
Why has my download link expired?
Results are temporary: 2 hours for guests and 7 days in signed-in history. The result is deleted after expiry, so the old link cannot be revived. Recompress the original source to make a new result.
Will I lose credits if compression fails?
No. Credits reserved for a failed processing job are returned automatically and in full, once per job. Upload and download time do not use credits.
What should I do if the downloaded video has no sound or will not play?
Try a current player first. If it still fails, re-export the source as MP4 with H.264 video and AAC audio, then compress that copy. This removes many unusual codec, audio-track and timestamp combinations that older players reject.
Compress another video or check the current plans and file-size limits.