FAILED_DOWNLOADING_VIDEO / 2207052
Threads could not download the image or video used to create the media container.
Fix: Retry once. If Threads still cannot fetch it, re-upload the file to PublishQ and publish the new media item.
Threads accepts text, images, videos, and mixed carousels. Its API can rescale images during processing, so the key constraints are file size, supported format, aspect ratio, carousel count, and the rolling daily publishing quota.
Updated July 2026
Recommended sizes
Use these sizes when you need a sensible default. The tables below cover the limits enforced by the API.
Square image
1080×1080 (1:1)
A good feed image size; Threads may rescale larger images.
Vertical video
1080×1920 (9:16)
The recommended full-screen video ratio.
Documented image processing
320–1440px wide
This is a rescaling range, not necessarily a hard source rejection.
API limits
Check these values in your upload validator or before an agent submits a post.
Threads image processing and carousel constraints.
Threads video, copy, and discovery settings.
Rolling account-level publishing limits.
Common publishing errors
Find the returned code or the closest matching failure below, then fix the cause before retrying the post.
Threads could not download the image or video used to create the media container.
Fix: Retry once. If Threads still cannot fetch it, re-upload the file to PublishQ and publish the new media item.
The video aspect ratio failed Threads processing. The API returns ASPEC with this spelling.
Fix: Re-encode the video with a supported aspect ratio and create a new container.
The submitted video is longer than the Threads duration limit.
Fix: Trim the video to 5 minutes or less, then create and publish a new container.
The video bitrate is not accepted by the Threads media processor.
Fix: Re-encode the video with a standard web bitrate and upload it through a new container.
The Threads version is longer than the platform’s 500-character allowance.
Fix: Write a shorter Threads override instead of sending a caption written for a platform with a larger limit.
The Instagram account linked to Threads is restricted, which also blocks Threads publishing.
Fix: Check Account Status in Instagram and resolve the restriction before posting to Threads again.
Send PublishQ the post. We check it, prepare the media, and deliver it to Threads. You can work in the dashboard or connect through the API, CLI, or MCP server.
Common questions about Threads media sizes and API publishing limits.
1080×1080 works well for square Threads posts. Threads documents a 320–1440px processing width and can rescale larger supported images rather than rejecting them solely for resolution.
Threads accepts MP4 or MOV video up to 1 GB and 5 minutes, with a documented maximum width of 1920px.
Agents can send Threads posts through the PublishQ API or MCP server. PublishQ creates the media containers, polls their status, and applies the platform settings.
API reference for Threads API.
See exactly how your posts will look on Twitter, Instagram, LinkedIn, TikTok, and more before you publish. No signup required.
Preview how your post looks on each platform, customize the text per account if needed, then publish or schedule to all of them at once.
Write different text for each platform in a single post. Shorten for Twitter, go long on LinkedIn, add hashtags for Instagram — without creating separate posts.
Schedule posts, manage accounts, and upload media programmatically. Build your own integrations, automate workflows, or connect PublishQ to your existing tools.
Schedule text, image, and video posts to Threads. Add a topic tag to help your post get discovered. Stay active without the extra effort.