--- title: "Troubleshooting video uploads in Buffer" description: "If you're having trouble uploading or publishing a video in Buffer, this guide will help you troubleshoot common issues like failed uploads, slow processing, or video posts not appearing as expected." canonical_url: "https://support.buffer.com/articles/troubleshooting-video-uploads-in-buffer-LK0CldlFNB" md_url: "https://support.buffer.com/articles/troubleshooting-video-uploads-in-buffer-LK0CldlFNB.md" --- # Troubleshooting video uploads in Buffer If you're having trouble uploading or publishing a video in Buffer, this guide will help you troubleshoot common issues like failed uploads, slow processing, or video posts not appearing as expected. The most common issues come from using videos outside of the suggested requirements, so be sure to check the limits below before proceeding to other troubleshooting steps! ## Check your video format and requirements first Before uploading, make sure your video meets the specifications below. Most upload issues are caused by the video codec (the way the file is encoded), rather than its file size. You can check your video’s format, codec, resolution, and file size using a free tool such as [MediaInfoOnline](https://mediaarea.net/MediaInfoOnline). Video specifications: * **Codec: H.264.** This is the most important setting. Video recorded on an iPhone or Mac is usually **HEVC (H.265)**, which often fails to upload to Buffer. Re-encode to H.264 if you're not sure. * **Format:** MP4, MOV, AVI, or M4V. MP4 (H.264) is the most reliable. * **Resolution:** up to 1080p (1920px on the longest side). Videos larger than 1080p are downscaled during processing. 720p (1280×720) uploads and processes the fastest. * **Video bitrate:** ideally under **25 Mbps** (aim for 20–25 Mbps or lower for 720p), especially for Threads, Facebook, LinkedIn, and X/Twitter. * **Audio:** AAC codec, bitrate 128–192 kbps. **Maximum file size** (varies by network): * 40MB for Mastodon * 100MB for Bluesky * 300MB for Instagram * 1GB for Facebook, X/Twitter, LinkedIn, Pinterest, TikTok, and Threads * 10GB for YouTube Shorts **Avoid raw or high-end camera formats** such as ProRes, HEVC (H.265), AV1, or RED. These can fail even when the file size and length are within limits. :::info **Note:** If your video is too large, too long, or uses an unsupported codec, it may fail to upload or fail to publish. Length and aspect-ratio limits differ by network, so also check [Video size, length, and aspect ratio by network](https://support.buffer.com/en-us/articles/troubleshooting-video-uploads-in-buffer-LK0CldlFNB#h-video-size-length-and-aspect-ratio-by-network). ::: ## My video is stuck at 0% or won't upload to Buffer If a video stays at 0%, hangs during upload, or shows an error such as “Thumbnail generation failed for \[filename\]” or “Upload stalled for 60 seconds, aborting,” the issue is occurring while the video is being uploaded to Buffer, before the post is sent to the social network. The most common cause is the video codec. Start by re-encoding videos from HEVC (H.265) to H.264. Buffer uses your browser’s video decoder to generate the upload preview, and some browsers, especially Chrome on older macOS versions or restricted work and virtual desktop environments, cannot decode HEVC, ProRes, or AV1 files. When this happens, the upload may remain at 0% or fail during thumbnail generation. Because iPhones and Macs often record video in HEVC by default, this is a common cause of upload issues. Try the following steps in order: 1. **If the upload sticks at 0% or you see "Thumbnail generation failed," re-encode the video to H.264** (MP4, H.264 video, AAC audio) using a free tool like [HandBrake](https://handbrake.fr/) or QuickTime, then upload again. This resolves most stuck uploads. 2. **If re-encoding doesn't help, rule out your browser and network.** Try posting from an incognito/private window, disable ad blockers and browser extensions, turn off any VPN, and try a different network. [Learn how to open Buffer in an incognito window, safelist Buffer, and check your VPN](https://support.buffer.com/en-us/articles/opening-buffer-in-an-incognito-or-private-window-how-to-safelist-buffer-and-using-a-vpn-LQYq3oqS1e). 3. **If you're on a work computer or network,** check whether antivirus or security software (for example, Bitdefender), a corporate firewall or proxy, or a virtual desktop is blocking the upload. Try a personal device or network to confirm. A full device restart can also clear the **"Upload stalled for 60 seconds, aborting"** error. 4. **If it works in the mobile app but not on the web (or the reverse),** that points to a browser or network issue on the device that's failing, not your file. Use the device that works, or apply the browser and network steps above. 5. **If it still won't upload,** try a small test video (a few seconds of H.264) to confirm the account and connection are fine. :::tip **Tip:** Buffer transcodes and processes video as it uploads, so large files and slow connections take longer. Uploading H.264 at 720p is the fastest, most reliable combination. ::: ## Video size, length, and aspect ratio by network A video can meet the file size and codec requirements yet still be rejected due to its length or aspect ratio. These limits are set by each social network’s API, so they apply to all scheduling tools, not just Buffer. Aspect ratio, which refers to the shape of the video or image, is a common cause of rejection: * **Instagram** supports aspect ratios from **4:5** to **1.91:1** for automatic publishing. Although Instagram’s grid now displays posts in a 3:4 format, its API does not yet accept 3:4 uploads. To avoid a failed post, crop 3:4 media to 4:5 before scheduling. See [Instagram's accepted aspect ratio ranges](https://support.buffer.com/en-us/articles/instagrams-accepted-aspect-ratio-ranges-Frc2Xqewbd). * **Reels (Instagram and Facebook)** need a vertical **9:16** video. Videos that do not use this exact aspect ratio will be rejected. * **YouTube Shorts** require an exact **1:1** or **9:16** aspect ratio, such as 1080 × 1080 or 1080 × 1920. YouTube’s API is stricter than its native uploader, so a slightly different size, such as 1078 × 1920, may upload directly to YouTube but still be rejected when published through Buffer. * **LinkedIn** accepts video aspect ratios from **9:16** (tallest) to **16:9** (widest). * **Pinterest** supports **1:1** square videos (which is recommended), as well as vertical videos in **2:3**, **4:5**, or **9:16** aspect ratios. * **Mastodon** rejects any video whose total pixel count (width x height) exceeds 8,294,400 pixels (equivalent to 3840 x 2160), regardless of aspect ratio. Buffer's composer now catches this before scheduling, showing an error like "Video resolution 3024x4032 is too large for Mastodon," so you can resize the video first. Learn more about the requirements per social network in [Sharing your videos through Buffer](https://support.buffer.com/en-us/articles/sharing-videos-through-buffer-LOe2p2rnAI). ## Custom thumbnails, cover images, and video titles You cannot upload a separate image as a video thumbnail or cover in Buffer. On networks that support thumbnail selection, you can only choose a frame from the video itself. Choosing a video thumbnail: * **Instagram, TikTok, and Pinterest:** After uploading the video, select ***Edit Thumbnail*** in the composer to choose a frame from the video. * **Facebook, LinkedIn, YouTube, Mastodon, and Bluesky:** Custom thumbnail selection is not supported. These networks automatically choose the thumbnail, and this can't be overridden by any tool. If you need a specific cover image, try one of these workarounds: * Add the image as the first frame of the video before uploading, then select that frame using ***Edit Thumbnail***. * For Instagram and TikTok, use [notification publishing](https://support.buffer.com/en-us/articles/using-notification-publishing-gvZQiMxVa2), and manually add a video cover in the Instagram or TikTok apps when completing the post. Video titles are displayed differently depending on the social network: * **Facebook:** The title appears at the top of the video post. * **X/Twitter:** The title is used when the video exceeds X/Twitter’s file size limits and is displayed as a link to Buffer’s video player instead of a native video. * **Pinterest:** The title appears at the bottom of the video in the feed. :::info **If the *Edit Thumbnail* tool doesn't open or won't save:** the video may not be rendering in the editor (often a browser or codec issue). Confirm the video is H.264 (see [Check your video format and requirements first](https://support.buffer.com/en-us/articles/troubleshooting-video-uploads-in-buffer-LK0CldlFNB#h-check-your-video-format-and-requirements-first)), then try an incognito window. ::: :::tip **Tip:** If your post looks different from what you expected, [check the social network’s limitations](https://support.buffer.com/en-us/articles/sharing-videos-through-buffer-LOe2p2rnAI). A link preview often means the video didn’t meet the platform’s requirements. ::: ## Notification publishing, automatic publishing, and "Sent but not live" If a video appears not to publish, it may be set to notification publishing rather than having failed. Understanding the two publishing modes clears up a lot of confusion: * **Automatic publishing:** Buffer publishes the video for you at the scheduled time. * **Notification publishing:** At the scheduled time, Buffer sends a notification to the Buffer mobile app. You then complete the post manually in the social network’s app. If you do not complete the final steps in the app, the video will not be published. To check which publishing method a post uses, open it in Buffer and review the publishing setting. To switch to automatic publishing, open the post in the composer and select ***Automatic*** (where supported by the social network and post format). :::info **Note:** A post marked ***Sent*** in Buffer means it was handed off to the social network, but it does not always confirm that the post went live. If the post is not visible on your profile, check whether it was a notification post that still needs to be completed, whether the network returned an error, or whether Buffer is experiencing an outage (see our [status page](https://status.buffer.com/)). ::: ## Why does my video quality look lower after publishing through Buffer? When you publish a video through Buffer, it may undergo transcoding that can reduce quality, especially on networks like TikTok that support higher resolutions than our current default. **There is no setting to turn transcoding off**, so the goal is to upload a file that doesn't trigger it, and to expect some additional compression from the network itself. **Your video will be transcoded if it meets any of the following conditions:** * It uses HEVC (H.265) compression * Its video bitrate is above 25 Mbps * Its audio bitrate is above 128 kbps * Its audio uses one of these formats: AAC LC SBR, AAC LC SBR PS, ALAC (Apple Lossless), or PCM (uncompressed) * The video resolution is larger than 1080p (i.e., more than 1920px on its longest side) * It was uploaded via a mobile app (all mobile uploads are always transcoded) :::warning **To avoid quality loss,** encode your video so it doesn't trigger any of the conditions above, and upload from the Buffer web app rather than the mobile app, since mobile uploads are always transcoded. For TikTok specifically, the most common culprit is audio bitrate, so keeping it at 128 kbps or below can help avoid transcoding. ::: :::info **Note:** Even a perfectly optimized file will be compressed again by the social network when it publishes, so some quality difference from the original is normal and cannot be completely avoided. True 4K or very high-bitrate video isn't possible through the networks' publishing APIs. ::: ## Posting videos through the API, Zapier, Make, or n8n When publishing videos through Buffer’s API or an automation tool such as Zapier, Make, n8n, or a custom script, media requirements are stricter than when uploading manually. This can lead to a specific set of upload and publishing failures. * **Media must remain publicly accessible until the post publishes.** Buffer fetches the video from the URL you provide at publish time. If the URL expires, requires a login, or blocks external access, the post will fail. This can happen with Google Drive or Dropbox share links, or with CDNs that use hotlink protection. * The error **“Buffer API Error: #1030: Buffer could not fetch the image \[URL\]”** means Buffer’s servers could not access the media URL. Confirm the URL opens in a private browser window, and that your CDN, firewall, or WordPress host (for example, Cloudflare hotlink protection) allows Buffer to fetch it. * **Custom video thumbnails are not supported through the API.** Although the API accepts a thumbnail URL in the payload, Buffer does not apply it when publishing. * **We don't re-host media submitted through the API.** The file remains on your server, so the source URL must stay active and publicly accessible until publishing is complete. Learn more about [Using Buffer's API](https://support.buffer.com/en-us/articles/what-is-buffers-api-GtIYIQilz5) and [Using Zapier with Buffer](https://support.buffer.com/en-us/articles/using-zapier-with-buffer-EapRng2lI7). ## Platform limits and what isn't supported Some video features are limited by each social network's API, not by Buffer, so they can't be changed from our side. Understanding these limitations upfront can help you avoid unnecessary troubleshooting: * **X/Twitter:** videos are capped at about 140 seconds for third-party tools, including Buffer. This applies even to X Premium accounts; the longer-video limit only applies when you post directly on X. * **YouTube:** Buffer supports **Shorts** (vertical, up to \~3 minutes), not long-form or landscape YouTube videos. New or unverified YouTube accounts also have a daily upload limit set by YouTube. * **TikTok:** every post must include actual media; a link-only post fails. Video frame rate must be within TikTok's supported range (about 23–60fps), and a video that TikTok can't process may fail with a "file format" or "media not ready" error, cleared by recreating the post. * **Bluesky:** Videos published through Buffer must be 100 MB or smaller. Bluesky’s native app accepts larger files, but its API does not yet make that higher limit available to third-party tools. * **Facebook:** Publishing many videos in a short period can trigger Facebook’s rate limits or spam protection. This often appears as a generic or “unknown” error. Space out your posts and wait up to 24 hours before trying again. * **Google Business Profile:** **video isn't supported.** Google's API allows one image per post through third-party tools, so we're not able to publish video there. * **One media type per post:** a single post can contain images or a single video, not both mixed together, even where a network supports mixed media natively. If a limit is blocking something you need, let us know by [submitting a feature suggestion](https://suggestions.buffer.com/). ## Helpful tools for optimizing video files Smaller, well-formatted videos upload faster and are more likely to post without issues. Need to resize, convert, or compress your video (for example, to change HEVC to H.264)? These tools can help: * **[HandBrake](https://handbrake.fr/)** – Free desktop app for compressing and converting videos to H.264. * **[Clideo](https://clideo.com/compress-video)** – Quick online compressor to reduce file size. * **[VEED.io](https://www.veed.io/)** and **[Kapwing](https://www.kapwing.com/)** – Easy editors for trimming, resizing, or formatting for social media. :::tip **Tip:** Optimizing before upload speeds up processing and improves compatibility. To upload smoothly, use MP4 (H.264), keep the file under the network's size limit (1GB max, 300MB for Instagram), and stick to 1080p or lower (720p is fastest). ::: ## Quick checklist * ✅ Use MP4 with the **H.264** codec (re-encode HEVC/H.265 from iPhone or Mac) * ✅ Stay within the size, length, and aspect-ratio limits for each network * ✅ Keep video bitrate under 25 Mbps and audio bitrate under 192 kbps (AAC) * ✅ Avoid VPNs, ad blockers, and check for antivirus or firewall interference while uploading * ✅ Check for browser conflicts ([try incognito mode](https://support.buffer.com/en-us/articles/opening-buffer-in-an-incognito-or-private-window-how-to-safelist-buffer-and-using-a-vpn-LQYq3oqS1e)) * ✅ Upload from the web app (not mobile) for the best quality * ✅ Try a test upload with a small video * ✅ [Review how each network handles videos](https://support.buffer.com/en-us/articles/sharing-videos-through-buffer-LOe2p2rnAI) :::tip **Still need help?** Contact Buffer support at [hello@buffer.com](mailto:hello@buffer.com) with: * Your video's format, codec, size, and length * The social channel and whether you used automatic or notification publishing * What happened vs what you expected * Any error messages or screenshots :::