Your LinkedIn video can look sharp in the editor and turn into oatmeal after upload. The problem is usually a mismatch between frame size, bitrate, text design, and LinkedIn’s compression. In about 15 minutes, you can build a reusable preset that keeps captions readable, protects screen-recording detail, and avoids needlessly huge files. This guide gives you practical settings for talking heads, tutorials, product demos, and motion graphics, plus a quick file-size calculator before you render.
The Fast Export Recipe
For most LinkedIn posts, export an MP4 with H.264 video and AAC audio. Use 1080 × 1350 for a feed-friendly 4:5 post, 1080 × 1920 for vertical-first video, or 1920 × 1080 for wide slides and demos. Choose 30 fps unless your source was intentionally shot at 24, 25, or 60 fps.
- Codec: H.264 in MP4
- Video bitrate: 6–8 Mbps for most posts
- Audio: AAC, 48 kHz, 160–192 kbps
Apply in 60 seconds: Duplicate your current preset and name it “LinkedIn 1080 Crisp.”
Decision Card: Choose a Starting Preset
Talking head: 1080 × 1350, 30 fps, 6 Mbps target.
Vertical tutorial: 1080 × 1920, 30 fps, 7–9 Mbps target.
Slides or screen demo: 1920 × 1080, source-matched fps, 8–10 Mbps target.
Fast motion: Raise bitrate before raising resolution.
I once exported a 42-second announcement at nearly 600 MB because “maximum quality” sounded reassuring. The posted version looked no better than the 38 MB test. Bigger had merely become heavier luggage.
Who This Is For, and Who Needs Another Workflow
These settings suit creators, consultants, recruiters, educators, founders, and small teams posting native video to profiles or company pages. They are especially useful for clips under five minutes where text clarity and upload speed matter more than a cinema-style master.
Use a separate specification for paid video campaigns, LinkedIn Live, or agency deliverables. Those workflows may have different duration, caption, encoder, approval, and reporting requirements.
Your upload file should also not be your only master. Keep a higher-quality archive in ProRes, DNxHR, or another editing-friendly format. For a practical codec comparison, read H.264 vs. H.265 vs. DNxHD.
- Master: high quality and editing-friendly
- Upload: H.264 MP4 and compact
- Archive: project, fonts, graphics, and captions
Apply in 60 seconds: Add “MASTER” and “LINKEDIN” folders to your project template.
LinkedIn Upload Limits That Matter
LinkedIn Help currently lists native uploads from 75 KB to 5 GB, up to 15 minutes on desktop and 10 minutes in the mobile app. Accepted resolution runs from 256 × 144 to 4096 × 2304, with 10–60 fps and 192 kbps–30 Mbps.
These are boundaries, not recommended targets. A 5 GB file may fit, but so does a refrigerator through some doors. That does not make it a sensible carry-on.
The safest compatibility choice
Use MP4 with H.264 video. LinkedIn accepts multiple file types, but H.264 MP4 plays nicely with common editors, browsers, phones, and preview tools. It also gives you direct control over size.
Platform compression cannot be avoided
LinkedIn creates playback versions after upload. Give its encoder stable color, readable text, limited noise, and enough bitrate for real motion.
| Setting | Accepted | Practical target |
|---|---|---|
| Resolution | 256 × 144 to 4096 × 2304 | 1080-pixel delivery |
| Frame rate | 10–60 fps | 30 fps or match source |
| Bitrate | 192 kbps–30 Mbps | 6–10 Mbps for most 1080p |
| File size | 75 KB–5 GB | Often 30–150 MB |
Best Export Settings for Most Posts
Use H.264, progressive scan, square pixels, VBR encoding, AAC audio, and Rec. 709 SDR. This combination is ordinary in the best possible way: it works.
Visual Guide: The Clean Export Path
Pick 4:5, 9:16, or 16:9 first.
Use bold text and restrained motion.
Export H.264 at 6–10 Mbps.
Watch at real phone size.
Recommended baseline
- Format: H.264 MP4
- Dimensions: 1080 × 1350, 1080 × 1920, or 1920 × 1080
- Frame rate: 30 fps or match the intentional source rate
- Field order: Progressive
- Pixel aspect: Square, 1.0
- Profile: High
- Bitrate: VBR, 6–8 Mbps target, 10–12 Mbps maximum
- Audio: AAC, 48 kHz, 160–192 kbps
- Color: Rec. 709 SDR for a standard workflow
A clean 1080 export preserves faces and large text without 4K bulk. On one client project, a 4K screen recording made labels worse because everything was scaled too small. Rebuilding at the final 1080 dimensions fixed it before bitrate entered the room.
Show me the nerdy details
H.264 stores visual changes across groups of frames. Stable backgrounds and clean edges leave more data for faces and type. Grain, particles, fine patterns, and rapid zooms consume bits quickly. A visually simple 7 Mbps file can preserve text better than a chaotic 12 Mbps file.
Pick the Right Frame Shape
Use 4:5 for general feed posts
A 1080 × 1350 frame gives interviews, explainers, and product demos generous screen presence without forcing every shot into a phone-shaped composition.
Use 9:16 for vertical-first clips
A 1080 × 1920 frame suits advice, demos, and event snippets. Cropping can vary by device, so keep faces, captions, and key graphics near the center.
Use 16:9 for slides and desktop demonstrations
A 1920 × 1080 frame fits webinars and wide screen captures. The tradeoff is smaller type in the feed. If a slide needs twelve bullets, the codec is not the villain. The slide has become a tiny conference room.
| Frame | Best for | Watch for |
|---|---|---|
| 1080 × 1350 | General feed posts | Top and bottom overlays |
| 1080 × 1920 | Vertical-first video | Device-dependent crop |
| 1920 × 1080 | Slides and screen demos | Small text in-feed |
For more composition help, see these vertical video editing lessons.
Keep Text Crisp After Compression
Compression damages thin strokes, tiny characters, busy backgrounds, and moving text first. Export settings can protect a good title, but they cannot rescue a six-point font whispering over confetti.
Design for phone size
For a 1080-wide frame, start headlines around 60–100 pixels and supporting copy around 38–56 pixels. Use medium, semibold, or bold weights with strong contrast.
Reduce fine detail
Avoid single-pixel lines, tiny chart labels, and decorative patterns behind copy. Zoom software interfaces before recording. On a dashboard demo, every label was visible on the editing monitor but became decorative weather in the feed. Re-recording at 125% interface scaling solved it.
Crisp-Text Scorecard
- Readable at 25% preview size
- Medium weight or heavier
- Quiet background behind text
- Key lines thicker than one pixel
- Enough screen time to read twice
4–5 points: Test it. 2–3: Simplify. 0–1: Rebuild the graphic rather than feeding it more bitrate.
Screen-heavy creators may also want this guide to editing screen recordings with readable detail.
Short Story: The Subtitle That Passed Every Test Except the Phone
A consultant sent me a polished 75-second clip with tasteful gray captions, a pale blue background, and a font so thin it seemed to have excellent table manners. On the editing monitor, everything looked refined. The exported file also looked fine at full size. Then we uploaded it and watched on a phone in ordinary daylight. Half the words dissolved whenever the speaker moved, and the lowest caption line sat under interface controls. We did not increase bitrate. Instead, we changed the captions to semibold white, added a dark translucent panel, raised the text block, and shortened each line. The new file was smaller because we removed animated texture behind the captions. The lesson was useful: readability is a composition decision first and an encoding decision second. Test where the audience watches, not where the editor works.
Bitrate and File Size Without Guessing
Bitrate is the data used each second. For most 1080p LinkedIn posts, 6–10 Mbps balances detail and upload speed. Simple talking heads may look excellent at 5–6 Mbps. Fast movement, grain, crowds, foliage, and animation may need 8–12 Mbps.
VBR 1-pass or 2-pass?
Use VBR 1-pass for speed. VBR 2-pass can use data more efficiently when size matters, though short clips may look similar.
Mini Calculator: Estimate File Size
Estimated file size: 55.6 MB
The mental formula is total Mbps × seconds ÷ 8. A one-minute file around 7.2 Mbps lands near 54 MB before small overhead. This is why a short post does not need to be half a gigabyte.
- 5–6 Mbps: simple scenes
- 6–10 Mbps: most posts
- 10–12 Mbps: demanding motion
Apply in 60 seconds: Export the hardest 10 seconds at 6, 8, and 10 Mbps.
Audio and Captions for Mobile Viewing
Use AAC at 48 kHz and 160–192 kbps. Keep dialogue clear, avoid clipping, and check phone speakers because many viewers watch muted or in noisy rooms.
On a recruitment video, the voice sounded rich in headphones but vanished on a phone because the music occupied the same frequency range. Lowering the music helped more than any export switch. The codec was innocent for once.
Burned-in captions or caption files?
Burned-in captions guarantee your styling and placement. Caption files can improve accessibility and user control, although visual formatting may be limited. Keep an accurate SRT file and a separate burned-in version when exact placement matters.
- Use no more than two caption lines when possible.
- Break lines by phrase, not random character count.
- Keep captions away from the bottom edge.
- Use a dark panel when footage is busy.
- Watch once without sound before posting.
For a fuller comparison, read burned-in captions versus sidecar captions.
Editor-Specific Export Recipes
Adobe Premiere Pro
Adobe’s export guidance offers Match Source presets. Choose H.264, confirm dimensions, set 6–8 Mbps target and 10–12 Mbps maximum, and use AAC at 48 kHz.
DaVinci Resolve
Choose MP4, H.264, final timeline resolution, and matched frame rate. Restrict quality to roughly 6,000–10,000 Kb/s for normal 1080p work. Export AAC at 48 kHz.
Final Cut Pro
Share a computer file using H.264 for broad compatibility. Set the project to final dimensions before export. Use Compressor when you need exact bitrate control.
CapCut, Canva, and browser editors
Select 1080p, 30 fps, and MP4 where available. Avoid 4K by reflex. If a 30-second talking-head clip is several hundred megabytes, the preset is spending lavishly without buying visible quality.
Keep color predictable
Use Rec. 709 SDR for a standard workflow. HDR phone footage can shift brightness or color when apps interpret it differently. One creator’s video looked perfect in the editor and washed out after posting. A consistent Rec. 709 timeline and output fixed it. See how to avoid gamma shifts during upload.
Common Export Mistakes
Exporting 4K just because the source is 4K
Keep 4K for reframing and archives, but compare a 1080 delivery copy first.
Using H.265 for every post
H.265 can be efficient, but H.264 MP4 remains the easier compatibility choice.
Changing frame rate without a reason
Match the source or timeline. Converting 24 fps to 30 fps does not create real motion detail.
Shrinking a finished composition
Rebuild title placement for each frame instead of scaling the entire design like a photocopy.
Adding heavy grain
Fine random texture consumes bitrate and can become crawling blocks. Keep the artistic master and make a cleaner social copy.
Trusting only the editor preview
Watch the exported file locally, on a phone, and after LinkedIn finishes processing.
| Symptom | Likely cause | First fix |
|---|---|---|
| Soft captions | Text too small or thin | Increase size and weight |
| Blocky motion | Bitrate too low | Raise target by 2 Mbps |
| Washed-out color | HDR or gamma mismatch | Standardize Rec. 709 SDR |
| Huge file | Excess bitrate or 4K | Use 1080p at 6–10 Mbps |
- Soft text starts in design
- Blocky motion points to bitrate
- Color shifts point to color management
Apply in 60 seconds: Change one variable on a 10-second test segment.
When a Test Upload Beats More Tweaking
Once the file looks good locally, upload it. The processed version reveals crop behavior, caption clarity, and mobile audio balance.
- Watch the local export on a computer at normal size.
- Watch the same file on a phone without zooming.
- Watch the processed LinkedIn version after encoding finishes.
Use the hardest ten seconds: smallest text, fastest movement, strongest gradient, or busiest background. Exporting the whole video repeatedly is a fine way to age in real time.
Seek an editor or color specialist when color shifts persist, correct-size text stays soft, audio clips, or hardware encoding creates artifacts. Bring the source, settings, preset, and posted sample.
Export Handoff Checklist
- Sequence dimensions and frame rate
- Codec and bitrate settings
- Source, timeline, and output color space
- Caption file and burned-in version
- Ten-second problem segment
- Screenshot of the posted result
FAQ
What is the best format for a LinkedIn video post?
Use MP4 with H.264 video and AAC audio for broad compatibility and predictable file size.
What resolution should I export for LinkedIn?
Use 1080 × 1350 for 4:5, 1080 × 1920 for vertical-first video, or 1920 × 1080 for wide slides and demos.
What bitrate is best for LinkedIn video?
Start at 6–8 Mbps for ordinary 1080p content. Use 8–12 Mbps for faster motion, grain, or dense animation.
Should I upload 4K video to LinkedIn?
You can, but 4K is not automatically sharper after processing. Compare a clean 1080 export first.
Is 30 fps or 60 fps better for LinkedIn?
Thirty fps is efficient for most posts. Keep 60 fps when the source intentionally uses it for fast movement.
Why does my LinkedIn video look blurry after upload?
Likely causes include tiny text, low bitrate for complex motion, repeated resizing, heavy noise, or incomplete processing.
How do I keep captions readable?
Use larger semibold text, strong contrast, short lines, a quiet background panel, and generous bottom clearance.
How small can the file be?
A 60-second 1080p clip at 6–8 Mbps often lands around 45–65 MB and can look excellent when the source is clean.
A Clean 15-Minute Routine
The sharp LinkedIn post from the opening is not hiding behind a magical quality switch. It comes from modest choices made in the right order: pick the final frame, make text sturdy, export H.264 at a sensible bitrate, keep audio clear, and inspect the processed upload on a phone.
Your next step takes less than 15 minutes. Export the hardest ten seconds at 1080 resolution and 7 Mbps, then compare a 9 Mbps version. Keep the smaller file when both look the same. That test can become a reliable preset for dozens of future posts.
Good social video is not the largest file you can produce. It is the smallest file that preserves what the viewer needs.
Last reviewed: 2026-07
