Skip to main content

Supported media types

Three upload paths share the same MIME set: WebM is intentionally excluded — every major social platform rejects it, so accepting it would just produce platform-specific publish failures.

Upload limits

| Type | Default cap |n| --------------------- | ------------------------- |n| Image | 10 MB per file |n| Video | 1 GB per file |n| MCP signed-URL upload | 50 MB per file (any type) | Files over 1 MB are sent in chunks (the dashboard streams them via Content-Range to the chunked upload endpoint) so big videos transfer reliably even on flaky connections. The MCP upload path uses a tighter cap on purpose — files route through the app server before being written to the configured storage disk, so a smaller ceiling keeps a single worker from being tied up by huge transfers. Each signed URL is single-use and expires after 15 minutes (configurable via MCP_UPLOAD_URL_TTL_MINUTES).

Platform content types and media requirements

Each platform supports different content formats with specific media requirements. Use GET /content-types for the live, machine-readable version.

LinkedIn / LinkedIn Page

X (Twitter)

Facebook

Instagram (and Instagram via Facebook)

TikTok

YouTube

Threads

Pinterest

Bluesky

Mastodon

Media ordering

Drag attachments in the post editor to reorder them. The order you set is the order they’ll appear on the social platform — important for carousels and multi-image posts.

File storagennKavio stores media in managed workspace storage. You do not need to configure storage infrastructure.nn## FAQ

10 MB per image and 1 GB per video by default. Files over 1 MB are sent through the chunked upload endpoint via Content-Range headers.
Each post stores its own media records. To reuse the same image, upload it again or copy from the asset library.
The media records are removed along with the post.
Kavio uploads media to social platforms as-is. Each platform applies its own compression and resizing rules afterwards.