June 26, 2026
LinkedIn Graphic Dimensions 2026: The Ultimate Guide
STOP!
Want an easy way to post on LinkedIn with an API?
Just use our unified social media API. One reliable endpoint for LinkedIn and 9 more platforms. Integrate in minutes and cut development time by 90%.
-
We manage auth, rate limits, and breaking API changes
-
Automatic retries and durable job queues
-
Fully white-labeled. Your audience never sees Mallary
-
Officially verified and approved to post on all platforms
fetch('https://mallary.ai/api/v1/post', {
method: 'POST',
headers: {
'Authorization': 'Bearer YOUR_API_KEY',
'Content-Type': 'application/json'
},
body: JSON.stringify({
platforms: ["linkedin"],
message: "Check out our new product!",
media: [{ url: "https://files.mallary.ai/launch-video.mp4" }],
comments_under_post: ["comment 1", "comment 2", "comment 3"],
auto_reply_enabled: true,
})
})You export a crisp banner from Figma, upload it to LinkedIn, and the live version looks wrong. The text sits too close to the edge, the profile photo covers the part you wanted people to notice, and the image that looked sharp on your canvas now feels soft in the feed.
That usually isn't a design problem. It's a rendering problem. LinkedIn doesn't just display files. It crops them, compresses them, masks them into circles, reuses them across desktop and mobile surfaces, and applies UI overlays that many design guides ignore.
Most articles on LinkedIn graphic dimensions stop at a list of pixel sizes. That isn't enough if you're building repeatable templates, shipping posts through an API, or managing content at scale. The useful version of this topic is a spec sheet: dimensions, aspect ratios, safe zones, file formats, and the practical reasons each rule exists.
Table of Contents
- Why Your LinkedIn Graphics Look Broken
- The 2026 LinkedIn Dimensions Quick Reference
- Universal Best Practices For All LinkedIn Graphics
- Personal Profile Images That Make An Impact
- Optimizing Your Company Page Visuals
- Mastering Post And Content Image Dimensions
- Designing For Display The Mobile Safe Zone
- Advanced Formats Video Documents And Ads
- Automating And Exporting Your Graphics
Why Your LinkedIn Graphics Look Broken
A LinkedIn image usually fails in one of four ways. It gets cropped differently than expected, blurred by upscaling or compression, obscured by interface elements, or reused in a placement you didn't design for.
The first mistake is treating the canvas as the final display. It isn't. A square profile photo becomes a circle. A cover image stretches across different viewport widths. A feed post may look balanced on desktop but lose the headline on mobile because the outer edges don't survive the transition cleanly.
The second mistake is exporting one master asset and assuming LinkedIn will adapt it gracefully. Platforms adapt mechanically, not tastefully. If the aspect ratio is off, LinkedIn will crop. If the source resolution is too low, LinkedIn will enlarge it. If the file format is poorly chosen, edges around text and logos will break down.
Practical rule: Design for the displayed shape, not the uploaded rectangle.
For developers, there's a second layer. If your app automates uploads, the media pipeline has to validate more than width and height. It should check aspect ratio, file size, transparency handling, and whether a given asset belongs to a personal profile, company page, or feed post workflow. A lot of publishing bugs come from sending a technically valid image to the wrong placement.
This is why LinkedIn graphic dimensions need to be handled like API contracts. A good file isn't just visually attractive. It's correctly sized, safely composed, and predictable after LinkedIn renders it.
The 2026 LinkedIn Dimensions Quick Reference
If you need a fast lookup, use this table first. If your team also publishes to other networks, this guide on mastering perfect image size is useful because it explains the broader web-image trade-offs behind export quality.
| Graphic Type | Recommended Dimensions (Pixels) | Aspect Ratio | Max File Size / Notes |
|---|---|---|---|
| Personal profile photo | 400 × 400 | 1:1 | LinkedIn accepts files from 268 × 268 up to 20,000 × 20,000. Maximum 8 MB. Circular crop applies. |
| Personal banner | 1584 × 396 | 4:1 | Maximum 8 MB. Design for overlap from the profile photo and variable viewport cropping. |
| Company logo | 400 × 400 | 1:1 | Maximum 4 MB for company logos. |
| Company cover image | 1128 × 191 | 5.91:1 | Official company cover size. Some modern displays render this much larger, so low-resolution exports can look soft. |
| Group banner | 1536 × 768 | 2:1 | Different placement from personal and company banners. Don't reuse other cover assets blindly. |
| Square post image | 1200 × 1200 | 1:1 | Stable format for many feed posts and carousels. |
| Vertical post image | 1080 × 1350 | 4:5 | Strong mobile format. Keep critical content centered. |
| Link preview image | 1200 × 627 | 1.91:1 | Best for article and URL shares. |
| Carousel slide | 1200 × 1200 | 1:1 | Keep consistent slide dimensions across the set. |
| Video thumbnail | Match video framing intent | Varies | Use high-clarity exports and center key text or faces. |
The quick reference is enough for a one-off post. It isn't enough for a team that builds templates, automations, or reusable design systems. That's where the rendering details matter.
Universal Best Practices For All LinkedIn Graphics
A common failure case looks like this. The design file is sharp in Figma, the uploaded image looks soft on mobile, the text sits too close to the edge, and the company logo gets clipped or recompressed into a fuzzy block. The root problem usually is not the design itself. It is the handoff between design, export, and LinkedIn's rendering pipeline.
Use PNG as the default for any asset with text, logos, icons, UI elements, or hard edges. PNG preserves those edges better after upload and usually holds up better when LinkedIn applies its own processing. JPEG still works for photography, especially when file weight matters, but it is the wrong default for banners, branded graphics, and screenshots with labels.
File format is only part of the job. Composition matters just as much.
LinkedIn is increasingly mobile-first in how posts are consumed, and mobile cropping is less forgiving than many desktop previews suggest. Keep faces, logos, and text away from the outer margins. Center the important content inside a safe zone so the asset still works when the feed preview trims the top or sides. This matters more on taller images, which often get stronger feed presence because they occupy more vertical screen space before the user scrolls past.
That vertical bias has a practical implication for teams building repeatable templates. A 4:5 post image often wins more attention than a wide horizontal one, but only if the subject stays centered and the typography remains readable at phone width. If the design depends on small corner details, the format works against you.
Export size also needs operational discipline. LinkedIn accepts a wide range of upload dimensions, but undersized files still get scaled up and look soft on high-density displays. Oversized files create a different problem. They increase export time, slow automated media pipelines, and can push assets over LinkedIn's upload limits for profile, cover, or logo placements. Good teams encode those rules in templates and validators instead of relying on memory.
The practical baseline is simple:
- Build placement-specific templates instead of reusing one canvas across profile, company, and feed assets.
- Export PNG for text-heavy graphics, logos, and banners. Export JPEG for photographic images where smaller files matter more than edge clarity.
- Keep critical text and faces centered to survive mobile cropping and circular or constrained display masks.
- Prefer vertical feed creatives when the goal is on-screen presence, but test readability at mobile size before rollout.
- Add a preflight check in your publishing workflow to validate aspect ratio, pixel dimensions, and file size before upload.
- Store source files separately from publish-ready exports so your team can regenerate assets without cumulative compression loss.
If you automate publishing through the API, preflight is not optional. The API can accept a file that technically uploads but still performs poorly because the aspect ratio is wrong for the intended placement or the text falls outside the mobile-safe area. Treat media validation as part of content QA, not as a final design review.
Teams standardizing employee branding often solve weak profile photos the same way. They start from a higher quality source, then export for LinkedIn's actual display rules. If you need to transform everyday photos into professional LinkedIn portraits, do that before you build templates around them. A polished source image gives LinkedIn less opportunity to expose blur, compression artifacts, or bad crops.
Personal Profile Images That Make An Impact
Someone lands on your profile from search or a comment thread. LinkedIn gives you a few hundred milliseconds to look credible. The profile photo does identity work. The banner does positioning work. They need different design logic because LinkedIn masks, overlaps, and crops them differently.
Profile photos
Use a square source file built for a circular crop. LinkedIn's current profile photo guidance, file limits, and supported upload range have been documented by LA Growth Machine, but the practical rule is simpler. Export a clean 400 by 400 image, keep the face centered, and leave enough margin around the head so the circular mask does not cut into hair, shoulders, or glasses.
Small mistakes show up fast here. A tight crop can feel fine in the upload preview, then look cramped in comments, search results, and mobile profile headers where the avatar renders much smaller. Fine background details also break down at those sizes. Use a plain or lightly textured background, strong face lighting, and no text. Text inside a profile photo becomes illegible almost immediately.
Format choice matters. PNG usually holds edges better around hairlines, glasses, and jackets. JPEG is acceptable for photographic portraits if you need a smaller file, but aggressive compression creates ringing and softness around the face. LinkedIn will generate its own derivatives after upload, so starting from a cleaner source gives its image pipeline less damage to amplify.
If the original photo is weak, fix that before you crop. This guide on how to transform everyday photos into professional LinkedIn portraits is useful because it focuses on profile-ready output instead of generic retouching.
Personal banners
The personal banner is a wide, shallow canvas. It looks generous in design tools and much smaller on real devices. That mismatch is why banners that feel balanced on desktop often break on mobile.
The technical problem is overlap. Your profile photo sits on top of the banner, and the exact visual obstruction changes by surface. Desktop profiles, mobile profiles, search contexts, and profile previews do not all reveal the same portion of the image. Treat the lower-left area as blocked, and treat the far edges as unstable.
A safer composition uses priority zones:
- Lower-left: Background only. No text, no logo, no face.
- Center: Broad shapes, gradients, product texture, or simple supporting imagery.
- Upper-right to right-center: Best area for a short positioning line or secondary brand mark.
This is the mobile-first safe-zone mindset that a lot of size charts skip. The banner is not just 1584 by 396. It is 1584 by 396 with overlap, responsive cropping, and inconsistent viewport width. If the message matters, place it where the narrowest common rendering still preserves it.
Keep copy short. One line survives. A stacked headline, URL, and call to action usually does not. In practice, banners work best as context, not as ads.
This quick video shows the practical setup well before you export your final header.
Teams generating banners at scale should encode these constraints into the template itself. Define a no-text exclusion zone for the avatar overlap, lock the aspect ratio, and keep editable text layers inside the right-side safe area. If you automate asset generation through a design API or publishing pipeline, that one template decision prevents a large share of broken exports before they ever reach LinkedIn.
Optimizing Your Company Page Visuals
Company Pages trip people up because the assets look similar to personal profiles at a glance but follow different rules. Reusing personal graphics here is one of the fastest ways to get awkward crops.
Personal and company assets are not interchangeable
Company logos use the same 400 × 400 square standard as profile photos, but the surrounding context is different. The logo often appears smaller and in more compact surfaces, so intricate details that looked acceptable in a personal avatar can turn muddy when used as a company identity mark.
The larger mismatch is the cover. A personal banner uses 1584 × 396, while a company page cover uses 1128 × 191. That's a much flatter canvas. If you stretch or crop a personal banner to fit, composition usually breaks. Text becomes cramped, logos sit too close to edges, and the visual balance collapses.
| Asset Type | Personal Profile | Company Page |
|---|---|---|
| Main square identity image | 400 × 400 | 400 × 400 |
| Banner / cover image | 1584 × 396 | 1128 × 191 |
How to design for the narrow company cover
A company cover is closer to a panoramic strip than a traditional banner. That changes what works.
Dense layouts don't survive this placement well. A narrow cover rewards restraint: simple color fields, one product visual, one short phrase, or a subtle brand pattern. Teams that try to force campaign messaging, screenshots, and multiple logos into this space usually end up with a graphic that feels compressed before LinkedIn touches it.
A few practical rules help:
- Use one focal point: A single product visual or brand motif is stronger than a collage.
- Keep text short: Think headline, not paragraph.
- Avoid edge-critical elements: Different displays can expose or crop the edges differently.
- Test with the logo present: The page logo and UI frame change how the cover is perceived.
For design systems, it helps to maintain separate master components for personal banners and company covers even if the campaign theme is identical. Same palette, same campaign, different geometry.
Mastering Post And Content Image Dimensions
A post can look perfect in Figma and still underperform once LinkedIn compresses it, crops it, and renders it inside a mobile feed. Feed image specs are less about memorizing dimensions and more about matching the asset to the container LinkedIn serves.
Square posts and link previews
Use 1200 × 1200 for standalone square posts. It is stable, easy to templatize, and predictable across brand announcements, quote graphics, event promos, and simple educational slides.
Use 1200 × 627 for link previews. That ratio fits LinkedIn's URL card layout, where the image supports the headline and metadata instead of carrying the whole message. If you force a square creative into a link share workflow, LinkedIn will not treat it like a square feed image. The result is usually awkward cropping or a weak card with too much dead space.
This is a library problem as much as a design problem. Keep separate templates for native image posts and URL shares. Teams that want a broader implementation checklist can use this reference on how to boost engagement with proper LinkedIn post sizes, especially for comparing feed placements.
Vertical posts get more screen time
For organic feed posts, the format with the most upside is usually 4:5 at 1080 × 1350.
The reason is straightforward. Vertical images occupy more of the mobile viewport, so they interrupt scrolling more effectively than square or horizontal assets. That does not guarantee better results, but it does give the creative more visual weight before the user decides whether to keep reading.
As noted earlier, PostFast reported that 4:5 vertical posts outperformed square posts on mobile in LinkedIn's 2025 reporting, and it also recommended keeping vertical assets at at least 1080px wide. That width matters for image quality. Start lower and LinkedIn's recompression tends to soften text edges, flatten gradients, and introduce visible artifacts around logos and UI mockups.
A few production rules help vertical posts hold up in the feed:
- Keep the headline block centered. Vertical formats earn attention by size, but edge-placed text is more likely to feel cramped or get visually crowded by the feed UI.
- Export as PNG for text-heavy graphics. JPEG is fine for photographic posts, but PNG preserves sharp edges better on charts, screenshots, and typography.
- Avoid decorative borders. Thin frames often look uneven after compression and make any crop feel more obvious.
- Design one clear focal plane. A face, chart, stat, or product visual should dominate the first second of scanning.
The trade-off is real. Vertical assets win presence, but they give you less horizontal room for side-by-side comparisons, wide screenshots, or dense dashboard captures. If the source material is naturally wide, square often produces a cleaner result.
If your image is paired with long-form distribution instead of a native graphic post, this guide on publishing an article on LinkedIn helps align the visual with the publishing format.
Carousels and multi-asset workflows
Carousel posts fail for a simple reason. Slide geometry drifts.
Pick one aspect ratio and keep it fixed across the full set. Mixed dimensions create visible jumps between slides, and those jumps feel like rendering mistakes even when the files are technically valid. Square is still the easiest base for carousels because layout constraints stay symmetrical. Vertical carousels can work well for educational content, but repeated elements such as page numbers, headers, and CTA placement need strict consistency.
This matters even more if the workflow is automated. At the API layer, multi-asset publishing benefits from preflight validation before upload begins. Check dimensions, file type, color profile, byte size, and slide order before assembling the post payload. Catching one malformed asset early is much cheaper than debugging a failed publish call after the rest of the media has already processed.
Designing For Display The Mobile Safe Zone
A LinkedIn post can look perfect in Figma, pass export QA, and still fail in the feed because the mobile crop buries the headline, trims the speaker's face, or pushes the CTA into UI clutter. Mobile viewing drives the composition rules now. Earlier source material in this guide noted that LinkedIn usage is heavily mobile and that centered safe zones outperform edge-dependent layouts, so design decisions should start there rather than at full-canvas width.
Why safe zones belong in the template, not the review checklist
Safe zones are not a polish step. They are part of the spec.
LinkedIn's mobile surfaces introduce several failure points at once. Feed previews are smaller, surrounding interface elements compete for attention, and different placements can crop or scale the same asset differently. Text near the perimeter is the first thing to become unreadable. Faces cropped at the forehead or chin look like rendering mistakes, even when the file itself is valid.
The practical rule is simple. Keep text, logos, product UI callouts, and faces inside a centered working area that occupies roughly 70 to 80% of the frame. Treat the outer band as disposable space for background color, gradients, patterns, or imagery that can tolerate partial loss.
That standard matters beyond single-image posts. It affects document cover pages, video thumbnails, carousel title slides, event banners, and any automated creative variant that needs to survive feed compression without manual fixes.
A mobile-first safe zone standard that holds up in production
Use these rules when building templates:
- Center the message block. Headlines, subheads, logos, and CTA text should sit well inside the middle of the canvas.
- Assume the edges will get compromised. Use edge space for decorative elements, not for meaning.
- Design for thumb-scroll speed. Small labels, thin lines, and dense screenshots collapse quickly on phones.
- Stack content vertically. Mobile viewers parse top-to-bottom layouts faster than wide side-by-side compositions.
- Leave breathing room around faces and logos. Tight crops become awkward once the feed scales or trims the image.
There is a trade-off. Wide compositions feel more cinematic on desktop, especially for dashboards, team photos, and before-and-after comparisons. Mobile-safe compositions give up some of that drama in exchange for reliable readability. For LinkedIn, that is usually the right trade.
One sentence should survive at a glance. One subject should remain fully visible. If those two conditions fail on a phone, the design is not ready.
For teams automating asset generation, this is also where pure dimension checks stop being enough. The API can reject unsupported files or mismatched media metadata, but it will not tell you that the title sits 18 pixels from a crop boundary. Production systems need template constraints, safe-zone guides baked into exports, or post-render checks in the creative pipeline. If you are building that workflow programmatically, this guide to the LinkedIn API publishing workflow is the right companion read.
Advanced Formats Video Documents And Ads
Specialized LinkedIn formats create most of the operational edge cases. The dimensions matter, but so does understanding what the placement is trying to do.
Video and thumbnails
For native video, the thumbnail is often doing more persuasion than the motion itself. A weak thumbnail makes a strong video disappear in the feed. The simplest production rule is to match thumbnail composition to the video's intended framing and keep title text large, centered, and sparse.
Video assets also need more than image-level QA. In production pipelines, teams should verify poster frames, aspect-ratio consistency, and whether subtitles or text overlays drift too close to the crop boundary. If your app handles video publishing programmatically, this overview of the LinkedIn API and related publishing considerations is a useful companion for understanding the integration side.
Document posts
Document posts are one of LinkedIn's best formats for educational content because they turn a PDF into a swipeable sequence. The mistake is exporting a normal slide deck and assuming it will feel native.
A strong document post behaves like a carousel, not a presentation. That means larger headings, fewer words per page, repeatable margins, and a clear slide rhythm. If one page is dense and the next is minimal, the reading experience becomes uneven.
A few practical habits help:
- Design each page as a standalone panel: Don't rely on tiny speaker-note style text.
- Use consistent margins: Viewers notice alignment drift immediately in swipe formats.
- Front-load the hook: The first page has to sell the swipe.
Ads and campaign assets
Ad workflows are less forgiving because creative mismatches waste spend faster than they waste organic reach. The operational issue isn't only the dimensions themselves. It's that campaign builders often reuse organic assets without adapting message density, CTA placement, or crop tolerance.
For ad teams, the safest pattern is to maintain separate asset variants by placement. A post image, a link-card visual, and a carousel creative may share the same campaign concept, but they shouldn't share the same raw export.
This is also where file naming and metadata discipline matter. In agencies and larger SaaS teams, ad creative breaks less often when every asset encodes placement, ratio, and version in its filename or manifest. That's not glamorous, but it prevents expensive mix-ups.
Automating And Exporting Your Graphics
The teams that rarely ship broken LinkedIn visuals do one thing differently. They turn design rules into repeatable system rules.
Export settings that reduce avoidable issues
In Figma, Canva, and Photoshop, create dedicated export presets per placement instead of relying on manual resizing. A named frame for linkedin-profile-400, another for linkedin-banner-1584x396, and separate post templates for square, vertical, and link-preview assets remove a lot of human error.
Then lock down a few standards:
- Export PNG for text-heavy assets
- Keep aspect ratios fixed
- Reject undersized source files
- Store publish-ready files separately from editable masters
That separation matters. Designers need flexible masters. Publishing workflows need deterministic outputs.
Preflight checks before publish
For automation teams, preflight should happen before the job enters the queue. Check the dimensions, file weight, target placement, and media type before the publish request is made. If the asset is wrong, fail fast with a useful error.
The same principle applies to schedulers and campaign systems. If you're coordinating multi-network posts, a workflow that schedules posts to all platforms should validate the LinkedIn asset against LinkedIn rules rather than assuming one image will fit every destination.
LinkedIn graphic dimensions aren't just a designer's concern. They're a pipeline concern. The best-looking result usually comes from a boring, disciplined process: template correctly, export intentionally, validate automatically, publish once.
If you're building social publishing into a product or need a cleaner way to handle media validation, scheduling, and official API delivery, Mallary.ai gives teams a developer-first layer for managing that workflow without stitching together separate platform integrations by hand.
