Identify where the failure happened
There are three useful checkpoints: the site accepts a request, the browser receives a file, and the file plays. Record which checkpoint failed and the exact message. A working preview only proves that some information was returned; it does not prove that the complete file can be downloaded.
Check a known small file first
Save our 11,321-byte controlled MP4. It was generated for this site and is not a social-platform download. If it saves normally, your browser can receive at least this small static file from this website. That does not test large downloads, remote platform access, account restrictions or audio conversion.
Inspect it with the browser-only file checker. Expected dimensions are 320 × 180, with about one second of media. If your problem file behaves differently, keep both results in your report rather than repeatedly changing unrelated settings.
Match the message to the next step
| What you see | What to do next |
|---|---|
| Dangerous, suspicious or insecure download warning | Do not bypass the warning or disable protection. Check the source and report the warning text. |
| Disk full or insufficient permissions | Check available storage and use a destination you can write to. Retry only after correcting the local problem. |
| Network failure or interrupted transfer | Check your connection and the browser's download history. A retry can help a transient connection issue, not an access restriction. |
| Private, unavailable or unsupported source | Stop retrying. Ask the owner for an authorized copy; do not supply login cookies or a password to a downloader. |
| File saved but cannot play | Move to the format and playback checks rather than changing browser download permissions. |
Find the file before downloading again
Open the browser's download list and inspect the most recent entry, destination and status. A file may be in the device's Downloads folder without being imported into a photo library. A pending, canceled or zero-byte entry is not a completed copy. On a shared computer, confirm you are checking the same browser profile and folder used for the request.
Change one thing at a time
Keep the error text, try the controlled sample, check storage, and then compare in another current trusted browser if necessary. Avoid blanket clearing of cookies or all site data as a first step: it changes several conditions and may sign you out. Never install an unknown extension, certificate or app just because a download page asks you to.
A useful support report
Send the site page, approximate time and timezone, browser version, device type, exact message, and whether the controlled sample saved and opened. Include a public source URL only if you are comfortable sharing it and authorized to use it. Do not attach private media, passwords, session tokens or login cookies. Use Contact; file-reading failures are covered in our format guide.
Sources and scope
Source-linked revision; controlled examples are not live platform tests.
Found an outdated step? Report a correction. Read our editorial and testing policy.