Skip to main content

Supported Formats

Snipp supports a range of image and video formats for uploading and sharing. Ultra accounts and teams can also upload archives, audio and PDFs.

Images

Video

All uploaded videos are automatically remuxed to MP4 with the moov atom moved to the start of the file (faststart). This allows browsers to begin playback before the full file has downloaded. .mov and .mkv uploads are stored as .mp4 after processing, and the share URL reflects the new extension. If remuxing fails, the file is rejected as corrupt or unplayable.

Files (Ultra)

Files are available on Ultra and in teams. On other plans they fail with type unsupported_type, like any other unsupported format. Executables and app packages (.exe, .msi, .dmg, .apk, .jar and similar) are never accepted.
A post that contains a file is never public. If any file in an upload request is one of these, post-privacy: public is applied as unlisted to every post the request creates, and post.privacy in the response says so. Update Post returns 403 with type forbidden and Posts with files cannot be made public. when you try to make one public, and Add Files rejects files on a public post with unsupported_type. File URLs are always signed and expire after 24 hours, whatever the post’s privacy, and download under the file’s original name.

Discord Bot Uploads

The Snipp Discord bot is invite-only. Add it to your server or as a user app from snipp.gg/bot. There is no HTTP endpoint for the bot. The bot accepts images only (.png, .jpg, .webp, .gif). Videos are not supported through the bot. Upload those from the web uploader or the /upload endpoint.

File Size Limits

Maximum file size depends on your plan: Plus, Ultra and teams have no per-file limit: a single file can use everything left of the week’s allowance. Through the API and Relay, one request carries at most 50 GB, and bigger files go up in pieces (Large Files), so they have no cap either. A file larger than your limit fails with type file_too_large and File size exceeds the 50 MB limit. (with your own limit in place of 50 MB), like any other per-file failure. When it is the only file in the request the status is 413. When the whole request’s declared size already exceeds your weekly quota, it is refused up front with 413 and the same message.
Videos larger than 30 GB upload like any other file but always play in standard quality, without priority streaming.
Upgrading to Plus or Ultra removes the 50 MB per-file cap. Upload anything up to your full weekly quota in a single file.

Unsupported Files

The type is detected from the file’s own bytes, not its name or the declared content type. If you upload a file with an unsupported format, the API returns 400 with type unsupported_type:
In a multi-file upload the file is listed in failed instead, and the other files are still stored. See Partial upload failures.

Reserved Marker

Files that begin with an internal encryption marker are rejected by the upload endpoint with type unsupported_type and File starts with a reserved marker. If you encounter this error, the file may be corrupted or use a reserved byte sequence. Try re-exporting the file from its original source.