6_4ee4f2.png)
Upload Errors
File not uploading? Error during upload? Slow connection or timeout? Find the solution below.
Common upload errors
Select the error you're seeing to jump to the solution:
- Compress or archive the file
- Split into parts
- Check internet connection
- Try a different browser
- Disable extensions
- Check Wi-Fi or cable connection
- Disable VPN
- Restart router
- Pack in a ZIP archive
- Check blocked formats list
- Split file into smaller parts
- Use a faster connection
- Check file on source device
- Re-download and re-upload
File too large
When submitting a product, files are uploaded as part of the product release. The maximum size per upload is 500 MB per file. Files for buyers are typically delivered as ZIP archives — pack multiple files together into a single archive to keep things manageable.
Solutions when a file is too large
Video: HandBrake or FFmpeg — reduce resolution or bitrate.
Documents: Remove embedded high-resolution images.
Upload failed
The general "Upload failed" error can have multiple causes. Work through these steps in order:
-
Check the browser consolePress F12 → open the Console tab → attempt the upload again → look for red error text. Copy the error message — this is the most useful information to send to support.
-
Try a different browserSwitch to Chrome, Firefox, or Edge. If upload works in another browser, the issue is specific to your current browser's settings or extensions.
-
Disable browser extensionsAdBlock, uBlock Origin, Privacy Badger, and antivirus extensions can block uploads. Disable all extensions, then retry. Or open an incognito window (Ctrl+Shift+N) — extensions are off by default there.
-
Clear cache and cookiesCtrl+Shift+Delete → select Cached images and files and Cookies → All time → Clear data. Reload the page and retry.
-
Temporarily disable antivirus or firewallSome antivirus tools (Kaspersky, Norton, Windows Defender with strict settings) intercept upload requests. Temporarily disable them or add shookout.com to exceptions.
-
Try from a different device or networkIf nothing above works, test from a different computer or use mobile data instead of your home Wi-Fi. This isolates whether the issue is device-specific or network-specific.
Common console error codes:
- 413 Payload Too Large — file exceeds the size limit. Compress or split it.
- 401 Unauthorized — session expired. Log out and log back in.
- 500 Internal Server Error — server-side issue. Wait a few minutes and retry. Check shookout.com/status for outages.
- Failed to fetch / CORS error — network or extension blocking the request. Try incognito mode or a different browser.
Network error
Unstable internet is the most common cause of failed uploads for large files. The connection must stay active for the entire duration of the upload — any drop interrupts it.
Upload interrupted at 90%?
- Do not close the tab — wait 2–3 minutes to see if it recovers
- Uploads cannot be resumed from where they stopped — if it fails, you will need to start again
- For large files, split into smaller parts (e.g. 400 MB each) to reduce the risk of a full restart
Invalid file type
Some file types are blocked for security reasons — they cannot be uploaded directly. The solution in most cases is to pack the file inside a ZIP archive.
Packaging executable files for delivery
-
Add to a ZIP archiveRight-click the file → Add to archive (ZIP). This is the standard approach for delivering apps, plugins, and installers on shookout. Include a README.txt with installation instructions.
-
Add a README with instructionsTell buyers what the file is, how to extract it, and how to run it. Good documentation reduces support requests.
-
Use External Purchase for hosted softwareIf your software is hosted on GitHub, your own site, or another platform, use the External Purchase delivery option in the submission wizard to redirect buyers there directly.
ℹ️ Why these restrictions? Executable files can contain malicious code. Packaging them in a ZIP allows the archive to be delivered while making it clear to buyers that they are downloading something that requires manual execution. Always mention this clearly in your product description.
Request timeout
If an upload takes too long the server closes the connection. This typically happens with large files on slow connections.
- Split the file: Upload multiple 400 MB parts instead of one large file
- Upload during off-peak hours: Late night connections are typically faster and more stable
- Close other bandwidth-heavy apps: Video streaming, torrents, and large downloads compete with your upload speed
- Use Chrome or Edge: These browsers handle long-running uploads most reliably
- Keep the tab active: Some browsers throttle background tabs — keep the upload tab in focus
Upload time reference (approximate):
- 100 MB at 5 Mbps upload: ~3 minutes
- 250 MB at 5 Mbps upload: ~7 minutes
- 500 MB at 10 Mbps upload: ~7 minutes
- 500 MB at 5 Mbps upload: ~14 minutes
If your upload speed is under 5 Mbps, keep individual files below 200 MB.
File corrupted or not appearing after upload
If a file uploads but shows 0 bytes, disappears, or buyers report it won't open:
-
Verify the file on your own device firstOpen the file locally before uploading. If it doesn't open on your own machine, the file is already corrupted — re-download or re-export it from your source application.
-
Check the archive integrityFor ZIP/RAR archives, right-click → Test archive (7-Zip) to verify there are no errors inside the archive before uploading.
-
Re-uploadDelete the 0-byte file from your product and upload again. A connection drop at the very end of an upload can result in a corrupted file on the server.
-
If a buyer reports the file is brokenDownload the file yourself from My Purchases and test it. If it's corrupted on your end too, re-upload. If it works on your end, the buyer's download may have been interrupted — ask them to re-download from My Purchases.
Frequently Asked Questions
No — uploads cannot be resumed from where they stopped. If an upload is interrupted, you need to start from the beginning. To reduce the risk, split large files into parts (400 MB each) so that a failure only means re-uploading one part, not the entire file.
This is normal. After the file transfer completes, the server processes the file — antivirus scan, indexing, preview generation. For files around 500 MB this can take 1–5 minutes. Do not refresh the page. If it is still stuck after 10 minutes, refresh and check whether the file appears in your product.
Upload speed is determined by your upload bandwidth, not your download speed. Most home internet connections have asymmetric speeds — for example, 200 Mbps download but only 20 Mbps upload. Check your upload speed at speedtest.net. Also: close other apps using the internet, use Ethernet instead of Wi-Fi, and try during off-peak hours.
Yes, but with limitations. Mobile browsers — especially Safari on iOS — have size and file type restrictions. For product file uploads over 200 MB always use a desktop browser. Keep the screen on and the browser tab active during the upload.
The upload was received but may have failed processing — typically because of a corrupted file, an unsupported format inside a compressed archive, or a security scan rejection. Check your email for a notification with a rejection reason. If there is no email, contact support with the file name and approximate upload time.
You can add multiple files to a product release, but upload them one at a time for best reliability. Uploading several large files simultaneously splits your bandwidth and increases the risk of timeout errors.
Main rejection reasons: (1) Virus detected — file contains malicious code; (2) Prohibited content — file violates the Seller Agreement; (3) File corrupted — the uploaded file is unreadable; (4) Blocked format — the file type is on the restricted list (pack it in a ZIP instead).
Still can't get the file uploaded?
Open a support ticket with the error message from the browser console and we'll help you resolve it.
Contact Support