You export a video, upload it to Facebook, and it looks wrong the second it goes live. The top gets cropped in Feed. The Story version turns soft. The same file that looked clean in Premiere suddenly picks up black bars or muddy text after scheduling. Many assume Facebook is being inconsistent. Usually, the file is the problem.
That’s why facebook video size matters more than most guides admit. It’s not just about passing upload requirements. It’s about making one source file behave well across Feed, Reels, Stories, and the rest of your publishing stack without rebuilding the edit every time.
A lot of creators are also dealing with a second problem. They’re not publishing only to Facebook. They’re trying to push the same campaign to Instagram and TikTok from one workflow. If that sounds familiar, a practical video marketing for social media workflow matters just as much as knowing the raw specs. The ultimate goal is building a repeatable master-file setup that survives resizing, compression, and cross-posting.
Why Your Facebook Video Size Matters
The most common facebook video size mistake is simple. Someone edits for one placement and uploads that same file everywhere.
A horizontal promo gets pushed into Feed, then reused for Stories. A vertical Reel gets dropped into a feed post without adjusting framing. A square product demo looks acceptable on desktop, then wastes space on mobile. None of those failures are random. Facebook uses different placements, and each one rewards a native fit.
What bad sizing actually looks like
Here’s what usually goes wrong in real workflows:
- Cropping in the wrong places: Text placed too high or too low gets clipped when the same edit moves across placements.
- Black bars: A file that doesn’t match the placement ratio gets letterboxed or pillarboxed.
- Soft-looking footage: Facebook compresses uploads, so weak source exports often get worse after upload.
- Lower perceived quality: Even when the message is fine, the content looks less native in the feed.
That last one matters more than people think. Viewers don’t analyze aspect ratios. They just feel when a post looks out of place.
Practical rule: If your video doesn’t naturally fill the placement it’s uploaded to, Facebook has to compensate. That’s when quality and presentation start slipping.
Why this is a workflow problem, not just a design problem
Specs aren’t there to annoy editors. They’re guardrails. When you match the placement, you reduce avoidable damage during upload and make the post feel like it belongs where it appears.
That’s also why blindly exporting “one file for all social” usually fails. A single finished file can work, but only if you plan for that from the start. The master has to be chosen strategically, with enough flexibility for feed crops, vertical placements, and compression.
Most bad results come from skipping that planning step.
Facebook Video Specs Quick Reference Table 2026
A good spec table should help you choose a production path fast, not send you back into export hell. If your team schedules the same campaign across Facebook, Instagram, and TikTok, the goal is not to memorize every platform limit. The goal is to pick one master file that gives you clean crops for the placements that matter most.

Core specs by placement
| Placement | Recommended dimensions | Aspect ratio | Max file size | Practical duration guidance |
|---|---|---|---|---|
| Feed | 1080 x 1350 px | 4:5 | Up to 4GB | Works for both short edits and longer uploads, but short feed cuts are easier to retain attention with |
| Stories | 1080 x 1920 px | 9:16 | Up to 4GB | Keep it brief and front-load the message |
| Reels | 1080 x 1920 px | 9:16 | Up to 4GB | Shorter cuts usually hold better than stretched edits |
| In-Stream | 1080 x 1080 px or 1920 x 1080 px | 1:1 or 16:9 | Up to 4GB | Best suited to tighter, ad-style edits |
| Carousel video | 1080 x 1080 px | 1:1 | Up to 4GB | Use concise clips that can stand alone in sequence |
| 360 video | 4096 x 2048 px | 2:1 | Varies by format | Specialized format with separate handling requirements |
The specs I actually use in production
The table gives you the accepted formats. Production decisions are simpler than that.
For day-to-day publishing, I keep three numbers in my head: 4:5 for Feed, 9:16 for Stories and Reels, 1080-wide output for standard delivery. These dimensions address the placements social teams touch most often without forcing a custom export every time.
The export settings stay fairly stable too:
- File type: MP4 or MOV
- Codec: H.264
- Audio: AAC stereo
- Frame rate: 30fps is the safe default
Those settings are boring on purpose. Boring exports break less often.
Quick read on what to build first
If you only have time to produce one strong master, build for vertical-safe framing and protect the center of the composition. That gives you the best chance of cropping cleanly for Facebook Reels and Stories while still pulling a usable 4:5 feed version later through a scheduler like PostSyncer.
If you start with a locked horizontal edit, every downstream crop gets harder. Text placement gets tighter. Headroom disappears. Compression usually gets worse after multiple re-exports.
What to memorize
- Feed: 1080 x 1350, 4:5
- Stories and Reels: 1080 x 1920, 9:16
- Standard uploads: keep files under the common 4GB ceiling
- Safe export: MP4, H.264, AAC
- Best workflow: create one master with crop flexibility, then publish placement-specific versions from it
That last point matters more than another line in a spec table. Teams usually lose quality in the handoff between platforms, not in the original edit. A clean master file saves time, reduces rework, and gives Facebook less damage to add during compression.
Optimizing Video Specs for Each Placement
A video can meet Facebook’s upload rules and still look wrong in the actual placement. That is the problem worth solving.

The teams that waste the most time usually do the same thing. They export one version for Feed, another for Reels, another for Stories, then resize again for Instagram or TikTok. Every extra export is another chance to soften text, crush detail, or shift framing. If you schedule across platforms through a tool like PostSyncer, the better approach is to build one strong master file first, then crop from that source with intention.
Feed needs height, but not a full-screen vertical edit
For Feed, 1080 x 1350 px at 4:5 is still the format I’d choose for everyday posting. It earns more screen space on mobile than horizontal video and usually reads better than square for product demos, interviews, and captioned clips.
It also gives editors more practical room to work with lower-thirds, subtitles, and hands-in-frame shots.
If a brand publishes one feed format consistently, 4:5 is the safest operating default. It feels native without forcing every creative concept into a full vertical structure.
Stories and Reels punish lazy crops
1080 x 1920 px works best when the edit was planned for vertical viewing from the first cut. Trying to stretch a finished square or horizontal asset into 9:16 usually creates familiar problems: faces get pushed too close, text drifts into unsafe areas, and background fill makes the piece look recycled.
That is why I treat vertical as a production choice, not a resizing task.
If your source footage was not framed for it, use a clean clipping workflow before publishing. This guide on how to clip videos for different aspect ratios is a useful reference for building crops that hold up across placements.
In-Stream and carousel reward simpler layouts
In-Stream placements usually hold up better with 1:1 or 16:9, depending on the original footage. Carousel video is often cleaner at 1080 x 1080 px because the frame is tighter and easier to control.
These placements leave less room for edge-heavy design choices. Keep the subject centered, make text larger than you think you need, and avoid placing branding at the far margins where interface elements or cropping can interfere.
Build one master file, then crop down
Here is the workflow I use for mixed-platform campaigns:
| Goal | Better starting choice | Why |
|---|---|---|
| Facebook Feed priority | 4:5 master | Strong mobile feed presence without overcommitting to full-screen vertical |
| Reels and Stories priority | 9:16 master | Native framing for vertical viewing |
| Facebook, Instagram, and TikTok from one source | Vertical-safe master with protected center composition | Easier to create clean crops without repeated re-editing |
The hidden cost is not just time. It is quality loss from repeated compression. Re-export a file enough times and sharp footage starts looking soft before Facebook even processes it. TimeSkip's video compression guide explains that problem well, even though it covers YouTube.
A single master file strategy fixes a lot of that. Keep the key action, text, and logos inside the center-safe area, then create placement-specific crops from the same source instead of bouncing between resized exports. That is the setup that gives social teams speed without giving away quality.
Your Guide to Ideal Video Export Settings
A lot of Facebook quality problems are baked in before the file ever hits upload. I see it all the time with cross-platform campaigns. A team exports one version for Facebook, another for Instagram, then a rushed resize for TikTok. By the third pass, the file is already softer than the original, and Facebook still applies its own compression on top.

The better approach is to set up one strong master file, then create clean placement-specific crops from that source. That cuts re-exporting, keeps your workflow faster in schedulers like PostSyncer, and protects quality across Facebook, Instagram, and TikTok.
The export recipe I’d use for most Facebook uploads
For day-to-day publishing, this is the baseline I trust:
- Container: MP4 first. MOV only if your edit stack requires it
- Video codec: H.264
- Audio codec: AAC stereo
- Frame rate: 30fps, unless the source was intentionally shot for a different delivery frame rate
- Resolution: Export to the intended placement or from a master built for clean crops
- Bitrate approach: Keep enough data to hold detail, but do not inflate the file with unnecessary headroom
The goal is simple. Give Facebook a clean, standard file that does not need extra interpretation.
For multi-platform teams, I usually keep a high-quality master sequence with center-safe composition, then export delivery files from that source instead of making fresh edits for every channel. That one habit saves time and reduces the quality hit that comes from opening, resizing, and exporting the same creative over and over.
What causes quality loss during export
Bad exports usually come from workflow choices, not one dramatic mistake.
- Oversized exports for routine social posts: Extra pixels do not help if the final placement will crop or compress them away
- Odd codecs or wrappers: Standard delivery formats are easier for platforms to process consistently
- Unnecessary frame rate changes: Conforming footage too many times can create motion issues and extra rendering loss
- Aggressive compression on the first export: If text and edges already look weak locally, the uploaded version will look worse
- Multiple export generations from old deliverables: Every bounce from one compressed file to another strips detail
If your team keeps running into file size vs. quality trade-offs, TimeSkip's video compression guide is a useful reference. It covers YouTube, but the compression trade-offs apply here too.
A practical export workflow for short-form teams
This is the workflow I use when one source video needs to feed several placements:
- Start with the highest-quality original available.
- Build a master edit that protects the center area for vertical and square crops.
- Export one clean master delivery file.
- Create placement versions from that master, not from previously exported social files.
- Review each export on desktop and mobile before scheduling.
If your team is also cutting long recordings into social assets, a defined clipping process helps. Using a workflow for turning long footage into short clips keeps the edit focused on final placements early, which means fewer rescue crops at export time and fewer quality surprises later.
A quick visual walkthrough can help if your editor’s export panel still feels messy:
Fixing Common Facebook Video Upload Problems
A video can look clean in Premiere, then fall apart the second it hits Facebook. That usually traces back to one of four issues: the wrong aspect ratio, too much compression before upload, unsupported export settings, or a master file that was never built for multiple placements.
The fastest fix is to diagnose the file before you re-edit the creative.
My video has black bars
Black bars show up when the uploaded frame shape does not fit the placement. A wide 16:9 file dropped into a mobile-heavy Feed placement often gets letterboxed. A vertical file forced into the wrong container can create awkward padding too.
For Feed, a 4:5 version usually gives you the cleanest result on mobile.
Check these first:
- Sequence settings: Match the timeline to the final placement before export.
- Crop decisions: Reframe the shot for Feed instead of dropping in a horizontal asset unchanged.
- Text and graphics: Move captions, logos, and callouts after the crop so nothing feels squeezed.
If your team schedules one campaign across Facebook, Instagram, and TikTok, a master-file workflow saves time. Build one clean source edit, then create placement-specific versions from that master instead of forcing one finished export everywhere.
My upload looks blurry after publishing
Blur usually starts before Facebook touches the file. I see it most often when teams export from an already compressed social version, resize it again, then upload that second or third generation file.
Use this checklist:
- Export at the intended dimensions for the placement
- Use MP4 with H.264 for standard uploads
- Review the local file at 100% size before publishing
- Avoid tiny text and thin graphic lines that break apart after compression
Small quality losses add up fast when one asset gets reused across networks. A single strong master file keeps detail intact longer and cuts down on rescue exports later.
Facebook rejected my video
Rejections are often technical. The file may use an odd codec, carry export settings Facebook handles poorly, or come in too heavy after unnecessary re-encoding.
Start with the basics:
- Re-export as MP4
- Use standard H.264 encoding
- Remove unusual variable settings if your editor added them
- Keep the file size reasonable for the placement
- Rename the file and upload a fresh export instead of retrying a questionable one
If you publish through a Facebook video scheduling workflow, it also helps to standardize exports before anything enters the queue. That cuts down on failed uploads caused by last-minute edits from mixed tools.
My vertical video looks awkward in Feed
Feed problems usually come down to composition. The file may be technically valid, but the subject, subtitles, or product framing sit too close to the top and bottom edges.
A good master edit protects the center area from the start. That gives you room to create a Feed-friendly crop without chopping off faces, captions, or hooks in the first two seconds.
If a 9:16 video feels cramped in Feed, do not just resize the canvas and publish it again. Reframe the shot, reposition text, and export a dedicated version from the master. That extra step takes less time than fixing weak performance after launch.
How PostSyncer Auto-Formats Your Videos
The hard part of facebook video size isn’t memorizing specs. It’s managing the hidden cost of using one campaign asset across multiple platforms without chewing up editing time.

Most guides stop at Facebook’s native requirements. They don’t deal with what happens after you try to reuse the same vertical file for Instagram and TikTok, or when a feed-ready crop gets reprocessed in another app. That’s the expensive part of the workflow.
Why the master-file strategy matters more than another spec sheet
A practical multi-platform system starts with one strong source file, then adapts that file by placement. That’s different from exporting one finished version and forcing every network to accept it.
The reason is compression. Auto-resizing and re-encoding across platforms creates cascading quality loss, and Renderform’s write-up on Facebook dimensions notes that most guides don’t address that problem directly. The same source also points out that automating this process can save agencies 8 to 12 hours of production time monthly.
What smart formatting should handle for you
When teams use a scheduling workflow, the useful automation isn’t “upload once and hope.” It’s:
- Placement-aware resizing: Feed, Reels, and Stories shouldn’t all inherit the same final crop.
- Safer output handling: The source file needs adaptation that preserves composition as much as possible.
- Repeatable scheduling: Teams need the same result across client accounts, not manual fixes every week.
That’s where a platform such as PostSyncer’s Facebook scheduler fits logically into the workflow. It’s built around cross-platform publishing, so the operational goal is to work from a single source asset and adapt it for destination requirements instead of maintaining a pile of separate exports by hand.
A good master file reduces editing waste. A good scheduling workflow reduces formatting waste.
The setup I’d use for agencies and lean teams
If you publish across Facebook, Instagram, and TikTok regularly, use this approach:
| Workflow choice | What works | What usually fails |
|---|---|---|
| Source asset | High-quality master built for cropping flexibility | One finished export forced into every placement |
| Framing | Keep subject and text centered enough for alternate crops | Edge-heavy layouts that break outside the original ratio |
| Distribution | Platform-aware scheduling and resizing | Uploading the same file everywhere and fixing errors later |
The value isn’t just speed. It’s consistency. Teams stop rebuilding assets that should have been adaptable from the start.
The Ultimate Facebook Video Checklist
Before any upload goes live, run this quick pass. It catches most avoidable facebook video size mistakes.
Pre-production checks
- Choose the primary placement first: Decide whether the asset is really for Feed, Reels, Stories, or a mixed campaign.
- Pick one master orientation intentionally: If you need cross-platform flexibility, build with crop-safe framing from the start.
- Keep critical elements centered: Faces, product shots, captions, and logos shouldn’t depend on the outer edges.
Editing and export checks
- Match the sequence to the target placement: Don’t edit in one ratio and hope a crop fixes it later.
- Export in MP4 when possible: It’s the most practical default for predictable uploads.
- Use H.264 and AAC: Stable, common delivery settings avoid a lot of unnecessary failures.
- Stick with 30fps unless your workflow has a real reason not to: Consistency helps.
- Watch the export before uploading: Catch soft text, awkward crops, and audio issues locally.
Upload checks
- Confirm the placement version: Feed and vertical placements should not share the same final framing by accident.
- Check for bars or clipped text in preview: If it looks off before publishing, it won’t improve after publishing.
- Keep file size under Facebook’s standard cap for normal uploads: Don’t push the limit unless the format specifically requires it.
- Review on mobile, not just desktop: That’s where most fit problems become obvious.
The cleanest workflow is the one that prevents re-exporting. Good facebook video size decisions happen before the upload screen.
Frequently Asked Questions About Facebook Video
What is the best facebook video size for normal feed posts
For most mobile-first feed posts, 1080 x 1350 px in a 4:5 ratio is the strongest practical choice. It gives the post more screen presence than a wider video and usually looks more native in the feed.
What file format should I upload to Facebook
MP4 is the safest default. MOV is also commonly accepted, but MP4 with H.264 video and AAC audio is usually the easiest path for stable uploads and manageable file sizes.
Can I upload very long videos to Facebook
Yes, Facebook supports long-form uploads for some placements. The upper limit can reach 241 minutes for standard video types, based on the earlier cited source. That said, long support doesn’t mean long is the smartest default for social distribution.
Should I create one file for Facebook, Instagram, and TikTok
You can, but only if that file is built as a master source, not as a final locked delivery file. The safest approach is a high-quality master with crop-safe framing, then placement-specific adaptation during scheduling or export.
If the source is too tightly designed for one ratio, reuse becomes painful fast.
Why does my video look worse after upload than it does on my computer
Because Facebook recompresses uploads. If your source file is already over-compressed, undersized, or framed poorly for the placement, the uploaded version can look softer, harsher, or more awkward than the local export.
Do captions and on-screen text affect video quality
They can affect perceived quality more than technical quality. Thin fonts, tiny subtitles, and edge-hugging text often look fine in the editor and then become harder to read after upload compression or cropping. Use larger text and keep it away from risky edges.
What’s the safest single master file strategy
For teams publishing short-form content across several platforms, a vertical master usually gives the most flexibility, as long as the subject and text stay centered enough to adapt for feed crops. If Facebook Feed is the only serious destination, a dedicated 4:5 workflow is often cleaner.
Is the maximum file size always 4GB
For standard feed, in-stream, and carousel uploads, 4GB is the reliable working limit cited earlier. Some specialized formats have different rules, so treat standard uploads and specialized uploads separately instead of assuming one cap applies everywhere.
If your team is tired of re-exporting the same video for every network, PostSyncer is worth a look. It’s built for scheduling across major platforms from one workspace, which makes it useful for a master-file workflow where the goal is to create once, adapt cleanly, and publish without constant manual resizing.