Streamable Video Downloader

Because Streamable keeps one file per clip and adapts delivery around it. The downloader reports exactly what the platform exposes, which is a single best-source MP4. Adding a fake 1080p option would only hand you an upscaled file, so the list stays as short as the truth.

Only if the clip was stored that way, and in our measurements it was not: the test file came back at 852×480. Nothing is enlarged server-side. Check the downloaded file’s properties for the real number, whatever the streaming page looked like while it played back. If the figure matters for a project, check it before editing, not after.

Yes. The source file already contains both tracks, so the MP4 arrives with its AAC audio intact and plays with sound in any player. If the audio alone is what you need, take the MP3 entry from the same parse instead of the video entry. Both entries come out of one request, so nothing extra has to be fetched.

No. A protected clip needs a credential the anonymous parser does not have, so it fails at parse time rather than returning an empty file. Public clips, including ones you reached through an /e/ embed address, are the supported case here, and those are exactly what the format list describes.

You get a parse error, not a broken download. Streamable removes clips on its own schedule, and a dead id has nothing behind it to fetch. Re-copy the link from the live page if you still have access to it, then parse again, because an expired id cannot be revived by retrying.

Yes, the same parse lists an MP3 audio entry next to the MP4. Picking it skips the video stream, so you get the sound of the clip without the picture, which is usually what you want for a short reaction, a line of dialogue or a sound bite.

No watermark, no account and no daily download count. Concurrency is the one ceiling: two clips at a time service-wide, capped at one per address, so a burst of requests queues for a slot rather than being turned away with an error. Nothing else limits how many clips you save.