You export a video, upload it to Facebook, and the file passes validation. Then you reuse it for Stories, discover that the crop hides the speaker's face, and notice that the captions aren't available in another placement. Live creates a different problem entirely, because the upload workflow accepts settings that Facebook's live ingest rejects.
That situation is common because Facebook video requirements aren't one checklist anymore. Feed, Reels, Stories, In-Stream, Marketplace, Search Results, ads, and Live use different combinations of duration, aspect ratio, captions, and encoding rules. A technically valid Feed file can still be a poor Stories asset or an invalid Live stream.
This guide works as a practical lookup reference for creators, social media managers, advertisers, and production teams. Use the placement matrix when choosing an export, the encoding section when preparing files, and the troubleshooting section when Facebook re-encodes or rejects an upload. Teams comparing outside production support can also use this guide alongside resources on best video production companies to assess whether a partner understands distribution requirements, not just filming and editing.
Table of Contents
- Introduction to Facebook Video Requirements in 2026
- How Facebook Video Placements Are Categorized
- Universal File Foundations for Every Facebook Video
- Placement by Placement Specifications and Limits
- Recommended Encoding Settings for Clean Uploads
- Captions Subtitles Thumbnails and Cover Rules
- Common Upload Errors and How to Fix Them Fast
- Faster Publishing Workflow With SleekPost Optimization
- Quick Reference Lookup and Cross Reference Index
Introduction to Facebook Video Requirements in 2026
Meta's current documentation treats Facebook video as a collection of surfaces rather than a single destination. The documented Feed ceiling reaches up to 240 minutes, while Stories use a much shorter range and Live follows a separate ingest profile. Meta's placement chart also shows that caption support differs by surface, so a file can upload successfully and still lose an important accessibility feature when reused elsewhere. Meta's placement requirements provide the clearest starting point for that comparison.
Why one export causes several problems
A 16:9 interview edit is a sensible choice for horizontal Feed content. Reusing it in a vertical placement introduces different risks:
- The platform may crop the speaker or product.
- Text placed near the frame edges may sit beneath interface controls.
- Captions may not be supported in every destination.
- The opening may feel too slow when the asset appears in a short-form surface.
- A long edit may need trimming or restructuring rather than simple resizing.
The operational fix is to create a master edit, then derive placement versions from it. The master preserves the clean source, while each derivative gets its own crop, duration, subtitles, thumbnail, and publishing copy.
How to use this reference
Start with the placement table if you already know where the video will appear. Jump to the universal foundations if you need a reliable baseline export. Use the Live section inside the encoding guidance when you're streaming through an encoder, because Live doesn't use the same publishing path as an uploaded MP4.
The rest of the guide focuses on what passes technical checks and what prevents silent failures after upload. That distinction matters. Facebook may accept a file, but its automatic processing can still change framing, compression, captions, or playback behavior.
How Facebook Video Placements Are Categorized
Facebook's video ecosystem becomes easier to manage when you group placements by how viewers encounter them and how Meta processes the files. The useful categories are standard uploads, short-form vertical video, ephemeral content, Live ingest, and paid placements.
Standard uploads
Feed, Watch, Marketplace, and related video destinations can handle broader creative shapes and longer edits. Horizontal remains useful for interviews, demonstrations, webinars, and screen recordings, while square and vertical versions fit mobile browsing more naturally. Recent guidance includes 16:9, 1:1, 4:5, and 9:16 among the formats appearing across Facebook's video specifications. The Facebook format guide outlines that multi-format direction.
Standard uploads prioritize compatibility. A clean MP4 with H.264 video and AAC audio gives teams a dependable source for ordinary publishing, but it shouldn't automatically become the only version.
Short-form vertical video
Reels are designed around vertical viewing, with Meta recommending 1080p and support for H.264, H.265, VP9, and AV1. The preferred frame-rate window is 24 to 60 fps, while the composition still needs to account for interface overlays and fast mobile viewing. A vertical edit usually needs its own opening, text placement, and pacing.
Professional social media video production needs to include delivery planning. A production team that exports only one video file leaves the publishing team to solve cropping and subtitles at the last minute.
Ephemeral, live, and paid video
Stories are temporary vertical content, so duration and safe-area decisions become more restrictive. Live video is different again. Meta requires RTMPS, H.264 video, AAC audio, progressive scan, constant bitrate, and stereo audio at 44.1 kHz or 48 kHz for documented Live ingest. Meta's Live technical guidance explains those requirements.
Paid placements add another layer because the same creative may be delivered to Feed, Reels, Stories, or In-Stream. Treat the campaign as a set of renditions, not one file with a universal label.
Universal File Foundations for Every Facebook Video
Before choosing a crop or duration, make the source technically clean. Facebook can process many media combinations, but a production workflow should favor predictable inputs rather than testing every possible container and codec.
Start with a dependable container and codec
Use MP4 or MOV as the container. For broad compatibility, choose H.264 video with AAC audio. Meta's Reels guidance also supports H.265, VP9, and AV1, but H.264 remains the practical default when one file must move through different upload tools, ad systems, and scheduling workflows. Meta's Reels and video-ad guidance lists the relevant codec and export recommendations.
A sensible baseline looks like this:
- Container: MP4
- Video: H.264
- Audio: AAC stereo
- Audio sample rate: 44.1 kHz or 48 kHz
- Scan: Progressive
- Pixels: Square pixels
- Frame rate: Fixed, rather than an unpredictable variable rate
- Resolution: 1080p where the source supports it, or 1280×720 for a smaller baseline
H.265 can reduce storage pressure in some workflows, but it isn't the first choice when maximum compatibility matters. H.264 is easier to hand between editors, schedulers, advertising tools, and archive systems.
Keep the frame technically normal
Non-square pixels can stretch or compress the image after processing. Interlaced footage can create combing artifacts when Facebook generates web renditions. Variable frame timing can produce sync or playback problems, especially when a team moves the file through multiple transcoders.
Export the intended aspect ratio directly instead of relying on Facebook to decide how to fit the image. For content shot in a wide format, 1280×720 is a widely used recommended resolution, while higher-resolution exports can preserve more detail before re-encoding. The practical rule is simple: give Facebook a clean, correctly framed file rather than an unusual source that requires interpretation.
Large files also create a workflow problem before Facebook ever processes them. If your team regularly moves heavy masters between editors, clients, and publishing queues, a guide to large file uploads can help you plan transfer and storage steps separately from Facebook's final upload.
Placement by Placement Specifications and Limits
A file can pass Facebook's upload check and still fail as a placement. Feed, Marketplace, Stories, In-Stream, Search Results, Reels, and Ads apply different limits, crops, and caption behavior. Treat the master as a source file, then create versions for each destination instead of expecting one export to behave consistently everywhere.
| Placement | Max Duration | Aspect Ratios | Captions Supported |
|---|---|---|---|
| Feed | Up to 240 minutes | 16:9 to 9:16, including square and 4:5 formats | Supported |
| Marketplace | Up to 240 minutes | Placement-dependent feed formats | Not supported |
| Stories | 1 to 120 seconds | 1.91:1 to 9:16 | Supported in applicable workflows |
| In-Stream | 5 seconds to 10 minutes | Primarily horizontal formats | Supported |
| Search Results | Placement-dependent | Placement-dependent | Not supported |
| Reels | Meta recommends vertical 9:16 | 9:16 recommended, with other formats appearing in guidance | Supported through applicable workflows |
These values come from Meta's placement requirements chart, including the caption exclusions for Marketplace and Search Results. Check Review Meta's placement matrix before assigning one asset to several destinations.
Feed and Marketplace
Feed offers the widest framing range. Horizontal, square, 4:5, and vertical assets can appear in the broader Facebook video system, so select the ratio according to the subject and viewing context. A horizontal tutorial may need 16:9, while a presenter-led mobile edit may work better with a taller crop.
Marketplace does not support captions. If spoken explanation carries the message, add readable burned-in subtitles or revise the edit so the visuals communicate the main point without audio.
Reels and Stories
Reels favor a dedicated vertical 9:16 version. Meta's Reels guidance recommends an MP4 at 1080p and supports several modern codecs, although technical acceptance does not guarantee a useful crop. Keep faces, products, and important text away from the edges, where interface controls can cover them.
Stories need their own timing and composition decisions. A Feed edit may upload successfully, yet its opening can feel slow or horizontal footage can become unclear after automatic cropping. Use this guide to vertical video dimensions when preparing the vertical version.
In-Stream, Search Results, and cover assets
In-Stream accepts videos from 5 seconds to 10 minutes. An edit without a clear opening or suitable mid-roll context may technically pass while performing poorly in that placement. Search Results and Marketplace do not support captions according to Meta's chart, so place accessibility information inside the video or redesign the visuals.
Cover images and thumbnails must be checked in the destination's shape. A balanced 16:9 thumbnail can become unreadable in a vertical preview. Teams preparing launch assets can compare their workflow with these startup product video specs, especially when one message requires several aspect-ratio versions.
Recommended Encoding Settings for Clean Uploads
Accepted settings and preferred settings aren't identical. Facebook may process a file outside your favorite preset, but a predictable export reduces the amount of work the platform must do and gives its transcoder a cleaner starting point.
A dependable uploaded-video preset
For ordinary Feed, Reels, Stories, and ad uploads, use:
- Resolution: 1920×1080 for 16:9, 1280×720 for 16:9 HD, or a placement-specific vertical frame
- Container: MP4
- Video codec: H.264
- Audio codec: AAC stereo
- Audio sample rate: 44.1 kHz or 48 kHz
- Scan type: Progressive
- Pixel shape: Square
- Frame rate: Fixed and at or below 30 fps for ads
- Bitrate target: At least 3 Mbps for 720p30 or 6 Mbps for 1080p30, as stated in Meta's video-ad optimization guidance
A higher source resolution can preserve detail, but don't upscale a soft source and expect extra information to appear. Match the export to the footage and the destination.
Reels settings
For Reels, export a vertical 1080p file in MP4 with H.264 or H.265. Meta's preferred Reels frame-rate window is 24 to 60 fps, and the guidance specifies closed GOP settings of 2 to 5 seconds, square pixels, and progressive scan.
If the same creative is also going into ads, create an ad-specific version at or below 30 fps. That avoids asking one file to satisfy conflicting delivery preferences.
Live settings
Live uses a separate technical path. Configure the encoder for RTMPS, H.264 video, AAC audio, progressive scan, CBR, and stereo audio at 44.1 kHz or 48 kHz. Meta documents H.264 Level 4.1 for up to 1080p at 30 fps and Level 4.2 for 1080p at 60 fps.
Encoding rule: Don't send a normal uploaded-video preset to Live and assume Facebook will normalize it. Build and test a dedicated Live profile.
Captions Subtitles Thumbnails and Cover Rules
A valid file can still fail the communication test. Viewers may encounter the video without sound, in a cropped preview, or in a placement where uploaded captions aren't available. Packaging belongs in the export plan, not as an afterthought.
Choose the right subtitle method
Use platform captions when the placement and publishing tool support them. Keep a clean subtitle file with the project so the publishing team can attach it during upload. For Marketplace and Search Results, Meta's placement chart says captions aren't supported, so use burned-in subtitles when spoken content is essential.
Burned-in text must survive multiple crops. Place it inside a central safe area, avoid the extreme top and bottom of vertical frames, and preview the rendered video rather than relying only on the editing canvas.
A square or horizontal master with captions near the lower edge may look fine in Feed. When cropped to 9:16, those captions can disappear beneath interface elements. Build subtitle placement around the narrowest version you'll publish.
Thumbnails and cover frames
Choose a cover that matches the video's aspect ratio. For vertical content, keep the subject and headline large enough to remain legible in a small preview. For horizontal content, use a frame with clear subject separation and avoid placing critical words at the edges.
Don't use a thumbnail that promises information the opening never delivers. The cover, first frame, and caption should make the same point, especially for product demonstrations and educational videos.
Your written post also needs room for context and accessibility notes. Keep the accompanying copy concise and review the platform's Facebook post character limit before adapting the same caption for other networks.
Common Upload Errors and How to Fix Them Fast
Upload errors usually come from a mismatch between the file and the placement, not from Facebook randomly rejecting a good export. Read the error alongside the publishing destination. A file that works as an uploaded Feed video may still fail as a Live source because Live checks different properties.
The usual failure patterns
The image looks stretched. The source probably uses non-square pixels or an incorrect display aspect ratio. Re-export with square pixels and set the intended frame dimensions explicitly.
The audio disappears or fails validation. The file may use an unsupported or unusual audio stream. Convert it to AAC stereo at 44.1 kHz or 48 kHz, then inspect the final file rather than the editing project.
Live disconnects or refuses the stream. Live expects RTMPS, H.264, AAC, progressive scan, CBR, and stereo audio. Replace a variable-bitrate Live profile with constant bitrate and verify the encoder's codec level.
The Live frame is rejected. Meta warns that ratios too far from 16:9 may not be supported. Normalize the source to a 16:9 frame before it reaches the Live ingest endpoint.
An ad upload behaves differently from an organic upload. Ads have their own optimization preferences, including a frame rate at or below 30 fps and bitrate benchmarks for 720p30 and 1080p30. Create a paid-placement export instead of recycling an edit designed only for organic Feed.
The crop removes the message. The file passed technically, but the creative wasn't versioned. Reframe the shot, move text into a safe area, and render a placement-specific derivative.
A preflight check for publishing teams
Before uploading, inspect the final file with your editing application or media inspection tool:
- Confirm the container is MP4 or MOV.
- Confirm the video and audio codecs.
- Check that pixels are square and the scan is progressive.
- Verify the frame rate is fixed.
- Compare the aspect ratio with the target placement.
- Listen through the first and last section for sync or missing audio.
- Preview the crop on a mobile-sized canvas.
- Attach captions only where the destination supports them.
A preflight check is faster than discovering a framing problem after a scheduled post has already processed.
Faster Publishing Workflow With SleekPost Optimization
The efficient workflow isn't “export once and post everywhere.” It's edit once, version deliberately, then publish from a controlled queue.
Start with a high-quality master that has clean framing, isolated audio, and no burned-in crop-specific elements. From that master, create a horizontal Feed version, a vertical Reels or Stories version, and an ad version when the campaign needs different frame-rate or copy treatment.
Build a versioning system
Name files by destination and export profile, not by vague labels such as “final video.” A practical naming pattern might include the campaign, subject, placement, aspect ratio, and date. Store the clean master separately from the derivatives so no one accidentally crops an already cropped file.
Batch the work:
- Prepare: Create all required aspect-ratio versions from the same edit.
- Package: Add placement-specific captions, thumbnails, and copy.
- Validate: Inspect every derivative against its destination.
- Queue: Schedule the approved versions together.
- Review: Check the live post and playback after processing.
A scheduler such as SleekPost can support Facebook scheduled and instant publishing, per-platform copy customization, recurring posts, media management, and publishing across multiple social platforms. Use it as the publishing layer, while your editor or transcoding workflow remains responsible for technical exports. Teams comparing scheduling options can review this Facebook post scheduler app guide.
Keep approval separate from encoding
The person approving the message doesn't need to change codec settings, and the person checking the file shouldn't rewrite the campaign promise. Use a short QA record with the target placement, file name, aspect ratio, duration, caption method, and approval status.
If a file is large, upload it early enough to allow processing and review. Don't wait until the scheduled moment to discover that Facebook has reframed the subject or removed captions.
Quick Reference Lookup and Cross Reference Index
Use this index when you need a fast decision rather than a full explanation.
Technical baseline
- Recommended containers: MP4 or MOV.
- Broad compatibility video codec: H.264.
- Supported Reels codecs in Meta's guidance: H.264, H.265, VP9, and AV1.
- Audio: AAC stereo at 44.1 kHz or 48 kHz.
- Scan and pixels: Progressive scan and square pixels.
- Standard baseline: 1280×720 at 16:9.
- Common formats: 16:9, 1:1, 4:5, and 9:16.
Placement lookup
- Feed: Up to 240 minutes, with broad aspect-ratio support.
- Marketplace: Up to 240 minutes, but captions aren't supported.
- Stories: 1 to 120 seconds, with vertical 9:16 as the practical target.
- In-Stream: 5 seconds to 10 minutes.
- Search Results: Captions aren't supported.
- Reels: Vertical 9:16 is the recommended composition, with 24 to 60 fps preferred in Meta's guidance.
- Live: RTMPS, H.264, AAC, CBR, progressive scan, stereo audio, and a 16:9 recommendation.
Glossary
GOP means Group of Pictures, the structure used to organize video frames. CBR means constant bitrate, which keeps the stream's data rate consistent and is required for Meta's documented Live ingest profile. RTMPS is the secure streaming protocol used to send Live video to Facebook.
For workflows that move video between platforms, this guide to sharing a YouTube video on Facebook can help distinguish uploaded media from link-based distribution. Keep the placement matrix beside your export presets, and update the presets when Meta changes its documentation.
SleekPost lets you schedule or publish Facebook videos, customize copy and media by platform, manage recurring posts, and organize content from a single dashboard. Visit SleekPost to turn your approved placement versions into a repeatable publishing queue instead of handling every upload manually.