You finish the edit, export the file, upload it to Facebook, and wait for processing. Then the problems show up. The video looks softer than it did in Premiere Pro. The thumbnail cuts off your headline. A vertical ad that looked clean in preview suddenly hides the product shot in feed.
That's usually not a creative problem. It's a settings problem.
Teams often don't miss because the idea was weak. They miss because Facebook video requirements are scattered across platform docs, tool guides, and old blog posts that blur together placements with different rules. Feed behaves differently from Stories. Ads behave differently from organic posts. Compression decisions that are fine for a talking-head clip can damage a cinematic export.
This guide fixes that. It gives you the practical version: the specs that matter, the export settings that hold up, the trade-offs behind aspect ratio choices, and the checks that catch errors before publish. If your content mix spans tutorials, ads, promos, webinars, and vertical social clips, it also helps to review broader content formats to dominate social media so the format matches the job.
For platform workflows and publishing updates, keep your eye on the LunaBloom AI blog, but lock in the rules below first. Facebook rewards clean preparation. Guessing gets expensive.
Stop Guessing Your Facebook Video Settings
A lot of upload issues start long before the file hits Facebook.
The editor exports the master in a high-quality preset built for YouTube. The social manager trims it for feed. Someone else duplicates it for Stories. By the time the file goes live, the version on Facebook doesn't match the version that was approved. Cropping is off, text sits too close to the edges, and compression gets blamed for decisions that resulted from bad setup.
That's why strong teams standardize before they publish. They don't wait until the upload fails to think about aspect ratio, duration, or codec. They decide placement first, then export to match it.
Practical rule: Start with the placement, not the source file. A great edit in the wrong format still underperforms.
The fastest way to tighten this up is to separate your Facebook output into three buckets:
- Feed content: Best when you need flexibility and a post that can live beyond the short-form cycle.
- Vertical short-form: Best for Reels and Stories where immersive framing matters more than cinematic width.
- Ad creative: Best handled as its own deliverable, not a cropped copy of your organic post.
When teams stop treating Facebook as one generic destination, quality problems drop fast. The right video settings aren't complicated. They just need to be intentional.
Facebook Video Specs Quick Reference Chart 2026
If you need the answer fast, use this as the at-a-glance version. It's the cheat sheet you keep open while exporting, scheduling, or QA'ing assets from a designer.
For those building repeatable workflows, the LunaBloom starter app is useful for turning approved creative into production-ready outputs faster.
| Placement | Aspect ratio | Resolution | File size | File type | Duration |
|---|---|---|---|---|---|
| Reels | 9:16 | 1080×1920 | Max 4GB | MP4, MOV | Max 90s |
| In-Stream Videos | 16:9 | 1920×1080 | Max 10GB | MP4, MOV | Max 240min |
| Stories | 9:16 | 1080×1920 | Max 4GB | MP4, MOV | Max 20s |
| Feed Videos | 16:9 or 1:1 | 1080p | Max 10GB | MP4, MOV | Max 240min |
| 360 Videos | 2:1 or 16:9 | 4096×2048 | Max 10GB | MP4, MOV | Max 240min |
Use the chart for speed. Use the rest of this guide for judgment, because the technical pass is only half the job. The other half is knowing when a setting is accepted versus when it's the smartest choice.
Universal Export Settings for Perfect Playback
Most Facebook delivery problems come down to four decisions: container, codec, frame rate, and compression. Get those right and the platform has far less opportunity to damage the file during processing.
Start with the universal baseline Facebook supports for feed video: H.264 compression, progressive scan, stereo AAC audio above 128 kbps, and an optimal frame rate of 30fps. Feed videos can run up to 240 minutes, with a recommended file size limit of 4GB, support a minimum resolution width of 120 pixels, and work best at 1080×1080 for square or 1080×1920 for vertical formats. Facebook also supports aspect ratios from 16:9 to 9:16, with 4:5 especially suited to mobile viewing, according to Sprout Social's video specs guide.
The export baseline that works
Here's the preset I'd hand to a team using Adobe Premiere Pro or DaVinci Resolve for most Facebook deliveries:
- Format: MP4
- Video codec: H.264
- Scan type: Progressive
- Frame rate: 30fps
- Audio codec: AAC
- Audio mix: Stereo
- Audio bitrate: Above 128 kbps
- Resolution: Match placement, not the original timeline
- Aspect ratio: Match placement exactly
- File review: Watch the exported file before upload
That preset won't solve everything, but it eliminates the common self-inflicted issues.
The real compression trade-off
This presents a common hurdle for teams. A cinematic file can look gorgeous in the editing suite and still fail on upload or come out heavier than it needs to be. The problem gets sharper when the project includes layered audio, dense motion, texture-heavy backgrounds, or synthetic visuals.
Creators working with layered audio and HD exports often run into the same problem: balancing 1080p+ cinematic video against Facebook's 4GB file size limit requires active bitrate and compression management, not default export settings, as noted in The Brief's Facebook video size discussion.
What works in practice:
- Export for destination: Don't upload a giant master if the delivery target is feed or Stories.
- Use test exports: Run a short proof export from the most visually complex section of the video.
- Protect detail selectively: Fast movement, gradients, smoke, hair, and text edges reveal compression problems first.
- Audit audio too: If your mix includes music, voiceover, ambient layers, and effects, make sure the final stereo render stays clean. This quick guide to audio file formats is a useful refresher when editors are debating codec and delivery choices.
If the file only looks good at a massive export size, the issue usually isn't Facebook. It's the render strategy.
For teams managing repeatable output pipelines, the LunaBloom app can simplify formatting and export consistency. Even then, QA still matters.
A copy-ready preset for editors
Use this as a house preset name in Premiere Pro or Resolve:
Facebook Master Delivery
- H.264 MP4
- Progressive
- 30fps
- Stereo AAC
- Audio bitrate above 128 kbps
- Resolution matched to placement
- Safe margins checked before export
- Final file reviewed on desktop and mobile
A preset like that does two things. It speeds up production, and it reduces the chance that every editor on the team makes slightly different assumptions.
A walkthrough helps if you're training newer editors on why these settings matter in practice:
Facebook Feed Video Requirements
A feed video usually fails before the export finishes.
The pattern is familiar. A team cuts one master file, posts it everywhere, and assumes Facebook will handle the rest. Then the 16:9 frame looks small on mobile, captions sit too close to the bottom, and the product shot that looked balanced in the edit feels cramped once the feed crops it. Feed gives you options, but it also punishes lazy formatting.
For feed, Facebook supports long uploads and large files, but the practical decision is format. Meta's video guidelines allow common feed ratios including 16:9, 1:1, and 4:5, and feed creative should be exported in high enough resolution to stay clean on mobile, with 1080 pixels on the shortest side as a safe working standard based on Meta's video ad specs.
Choose the ratio based on the job
The right ratio depends on what the footage needs to do in the feed, not what was easiest to export.
| Format | Use it for | Strength | Common failure |
|---|---|---|---|
| 16:9 | Interviews, webinars, screen demos, repurposed YouTube edits | Preserves wide compositions and screen detail | Occupies less feed space on phones |
| 1:1 | Organic posts, explainers, talking-head videos, simple promos | Reliable on both desktop and mobile | Feels visually flatter than 4:5 |
| 4:5 | Mobile-first campaigns, product features, short educational clips | Takes up more vertical feed space without going full-screen | Crops feel tight if the original edit was designed wide |
Use 16:9 if the footage depends on width. Screen recordings, side-by-side interviews, and product demos often break when forced into a taller canvas.
Use 1:1 if you need one dependable version that works across organic feed placements with minimal redesign.
Use 4:5 if feed visibility matters most. It gives you more on-screen real estate in mobile scroll, which usually improves the odds that the first frame gets noticed.
Feed cropping causes more problems than teams expect
Ad managers and editors regularly assume a feed upload will display exactly as exported. That assumption costs clarity.
Facebook feed can display videos differently across surfaces, and surrounding UI eats into the viewing area on mobile. The practical fix is simple. Keep text, logos, subtitles, and product callouts away from the outer edges, especially near the bottom portion of the frame where interface elements compete for space.
A good working rule is to design the center first. Decorative background elements can extend outward. Anything the viewer must read should stay comfortably inside your safe area.
Build feed versions on purpose
Do not cut a horizontal master, then try to rescue it at the end with an automatic crop.
Set the canvas before graphics are built. That changes everything. Lower thirds stay readable, headroom stays consistent, and product framing survives the export.
Use this production sequence:
- Pick the feed ratio before editing graphics.
- Review every text layer on a phone-sized preview.
- Create separate exports for 1:1 and 4:5 if both placements matter.
- Check the opening frame without sound. Feed autoplay often starts muted, so the first visual has to carry the message.
- Upload a draft and inspect it in the actual feed. Preview windows miss problems that show up after processing.
What belongs in feed
Feed handles a wider mix of content than Reels or Stories.
It works well for recorded webinars, founder clips, customer education, product walk-throughs, interview excerpts, and evergreen explainers. It is also the safest home for assets that need a little more breathing room than a fast vertical placement allows.
Feed is a weaker choice for creative that depends on full-screen vertical immersion or tiny design details. If the edit only works when every inch of the screen is controlled, it probably belongs in a different placement.
Facebook Reels and Stories Specs
Reels and Stories look similar at first glance because both are vertical and mobile-native. The differences matter in production.
For Stories, Facebook requires a 9:16 aspect ratio with a recommended resolution of 1080×1920 pixels, while technically supporting up to 1440×2560. Story videos are limited to 1 to 60 seconds and must stay under 4GB, based on Crowbert's breakdown of Facebook Story video format and size.
Stories demand precision
Stories are less forgiving than feed. The frame fills the screen, which means every design error gets amplified.
Use Stories when the message is quick, visual, and direct:
- Limited-time announcements
- Product teasers
- Behind-the-scenes clips
- Simple talking-head updates
What usually fails in Stories:
- Dense text blocks
- Horizontal video dropped onto a vertical canvas
- Tiny captions placed too low or too high
- Visuals that need time to breathe
A Story should communicate immediately. If the viewer has to decode the layout, the creative is already behind.
Reels need stronger pacing
Reels also favor 9:16 vertical creative, but the audience expectation is different. Stories can be casual and lightweight. Reels need a more deliberate editorial rhythm. Strong opening frames, tighter pacing, and cleaner visual hierarchy matter more.
Here's the practical difference between them:
| Placement | Best tone | Editing style | Design priority |
|---|---|---|---|
| Stories | Fast, direct, personal | Minimal edit friction | Clarity and readability |
| Reels | Intentional, performance-minded | Sharper pacing | Hook and retention |
When a team recuts one asset for both placements, I usually tell them to simplify the Story version and sharpen the Reel version. Same source footage. Different viewer behavior.
Keep your key subject, headline, and CTA away from the outer edges of a 9:16 frame. Full-screen placements punish sloppy spacing.
Safe-zone habits that save you later
A few habits prevent most vertical mistakes:
- Center the subject: Avoid placing faces, products, or text too close to the top or bottom interface areas.
- Shorten copy: A few strong words beat a sentence crammed into the frame.
- Preview on mobile: Vertical creative has to be reviewed where it will be watched.
- Design natively: Don't treat vertical as a crop job. Treat it as its own composition.
Stories and Reels reward creators who respect the format. They punish recycled horizontal assets.
Facebook Live and Ad Video Specs
Live video and paid video ads operate under different pressures. Live needs stability and clear delivery. Ads need precision because one bad crop can hide the exact thing you paid to show.
A critical consideration is that: Facebook may mask 9:16 vertical video ads to a 4:5 aspect ratio in the feed, which can crop important visuals, thumbnails, and calls-to-action. Facebook notes this behavior in its video requirements one-sheeter for advertisers.
The masked vertical ad problem
This catches a lot of teams because the uploaded file is technically valid. The ad runs. But the feed presentation doesn't show the full composition the designer expected.
That means:
- Product labels can get cut off
- Headline text near the top or bottom can disappear
- CTA framing can weaken
- Thumbnail composition can break
The fix is simple in concept and easy to ignore in practice. Design vertical ads so the critical message still works inside a 4:5-safe central zone, even if the uploaded asset is 9:16.
If the ad only works when every pixel of the 9:16 frame is visible, it isn't built safely for feed delivery.
How to build ad creative that survives placement changes
Use a two-layer mindset.
First, build the full 9:16 version for vertical placements. Then pressure-test it by asking whether the same message still works when the visible space tightens toward 4:5 in feed.
A good ad layout usually has:
- Primary subject in the center
- Headline high enough to be seen, but not pinned to the top edge
- CTA or product proof away from crop-risk zones
A weak ad layout usually depends on edge placement, tiny text, or a product shot that only works at full height.
For policy and account-side details that often matter once media goes live, teams should also keep documentation easy to access, including operational pages like LunaBloom's terms when they're reviewing tool usage and workflow responsibilities.
Live video priorities
Live is less about perfect polish and more about clean delivery under real conditions.
What works for Facebook Live:
- Stable framing
- Clear audio before anything else
- Simple overlays
- Moderation during the stream
- A replay that still makes sense after the event ends
What doesn't work:
- Overdesigned live graphics
- Weak microphones
- Unplanned scene changes
- Streams that begin before the host is ready
For Live, viewers forgive a lot visually. They don't forgive bad audio or chaos.
Optimizing Thumbnails and Captions for Success
A technically compliant video can still flop if nobody wants to click it or if viewers can't follow it without sound.
That's why thumbnails and captions aren't finishing touches. They're core packaging.
Thumbnails decide whether the video gets a chance
A good thumbnail does one job. It makes the right viewer curious without misleading them.
For Facebook, keep thumbnail choices simple:
- Match the thumbnail framing to the video's aspect ratio
- Use one focal point
- Make text large enough to read on mobile
- Avoid cluttered backgrounds
- Show the subject, product, or promise clearly
What usually fails is overdesigned creative. Tiny copy, three competing images, heavy branding, and low-contrast text all reduce clarity. A thumbnail isn't a poster. It's a decision trigger.
If the platform auto-selects a frame that weakens the video, replace it manually. Don't accept a bad first impression because the file itself is technically correct.
Captions are a usability feature
Captions make videos easier to follow in silent autoplay environments, but the practical benefit goes beyond that. They improve comprehension, reduce drop-off when audio isn't ideal, and help viewers stay with the message in noisy or quiet settings.
There are two common caption approaches:
| Caption type | Best for | Risk |
|---|---|---|
| Burned-in captions | Maximum visual control | Harder to revise later |
| SRT captions | Flexibility and cleaner updates | Styling control is more limited |
Burned-in captions are useful when design matters and every word needs intentional placement. SRT files are better when you need easy edits, multiple versions, or cleaner accessibility workflows.
A caption file that's slightly plain is better than stylish captions nobody can read.
What readable captions look like
The best caption style is boring in the right way:
- High contrast
- Short line length
- Predictable placement
- Clean timing
- Accurate punctuation and spelling
Don't let captions cover a speaker's mouth, product details, or the only visual proof in the frame. If your creative already carries text overlays, simplify one or the other. Viewers shouldn't have to choose which words to read.
Your Pre-Publish Checklist for Flawless Video
Good teams publish with a checklist because memory gets unreliable under deadline pressure.
A final pass catches the mistakes that sneak through when creative, editing, paid media, and approvals all happen in parallel.
The last review before upload
Run through these questions every time:
- Placement match: Does the aspect ratio and resolution match the exact Facebook placement?
- Codec check: Was the file exported as H.264 with progressive scan?
- Audio review: Is the audio stereo AAC, clean, balanced, and free of distortion?
- Size limit: Is the file within the platform limit for that placement?
- Duration check: Does the runtime fit the selected placement?
- Visual QA: Have you watched the full exported file for glitches, framing issues, and spelling errors?
- Caption pass: Are captions present, readable, and accurate?
- Thumbnail review: Does the thumbnail still work on mobile and in cropped previews?
- Policy check: Does the content comply with Facebook's content policies?
The practical yes-no test
If you want a fast decision standard, use this:
| Question | If no, then |
|---|---|
| Does the format match the placement? | Re-export before upload |
| Does the message survive crop risk? | Redesign layout |
| Is the audio clearly understandable? | Fix mix before publish |
| Does the thumbnail sell the video honestly? | Replace it |
| Are captions readable on a phone? | Revise them |
This kind of discipline saves more time than it costs.
For operational questions, edge cases, or support requests in your production workflow, keep a direct line to the LunaBloom contact page.
What flawless usually looks like
A flawless Facebook upload isn't magic. It's a file that was built for the destination, compressed intentionally, checked on mobile, and reviewed like a final product instead of an export artifact.
That's the difference between teams that keep fixing posts after launch and teams that publish once.
If you want to speed up the entire process from script to export-ready social video, LunaBloom AI helps create studio-quality videos with voiceovers, captions, thumbnails, localization, and social-ready formatting in minutes. It's built for creators, marketers, and teams that want polished Facebook videos without getting buried in production overhead.
