Use 1200 x 644 pixels for your LinkedIn article feature image and 1920 x 1080 pixels for your article cover image. If you only remember one number, remember 1200 x 644, because that's the image people judge first in the feed before they ever open your article.
If you're reading this, you're probably in the same spot many professionals hit at least once. The article is written, the headline is solid, you upload the image, and LinkedIn turns it into something blurry, cropped, or oddly framed. That usually happens because two different image slots get mixed together: the Feature Image that appears in the feed preview, and the Article Cover Image that appears as the header inside the article.
That distinction causes most of the confusion around LinkedIn article image size. People design one asset and expect it to work everywhere. It rarely does. The feed preview has one job, get the click. The in-article cover has another, set the visual tone once the reader has already opened the piece.
Get the first one wrong and your article can look weak before anyone reads a word. Get the second one wrong and the article itself feels sloppy after the click. Both matter, but they don't serve the same purpose.
Table of Contents
- Why Your LinkedIn Article Image Matters
- Quick Reference Guide to LinkedIn Article Image Sizes
- The Feature Image Perfecting Your Feed Preview
- The Article Cover Header Mastering the In-Article Experience
- Best Practices for Inline Article Images
- File Formats and Optimization for Fast Loading
- Troubleshooting Common LinkedIn Image Issues
Why Your LinkedIn Article Image Matters
A weak image can make a strong article look rushed. On LinkedIn, that first visual often carries the full burden of stopping the scroll, especially when your audience is moving fast through a crowded feed.
The most useful way to think about LinkedIn article image size is this: there are two primary canvases, not one. The feature image is the preview asset people see before they click. The article cover image is the larger header they see after they open the article. Treating them as interchangeable is the mistake that creates most feed blur, awkward crops, and off-center headers.
The mistake most people make
Many writers build a single 16:9 graphic, upload it once, and assume LinkedIn will display it cleanly in every context. It won't. A graphic that feels balanced as a wide header can lose impact when squeezed into a feed preview shape.
That's why I always separate the workflow:
- Design the feed asset first: This is the click driver. It needs to read fast and stay sharp.
- Design the article header second: This supports the article experience after the reader lands.
- Check both on mobile: Desktop can hide problems that become obvious on a phone.
Practical rule: If text placement only works in one layout, it isn't finished yet.
A good article image also signals editorial quality. Readers notice when branding is aligned, text is legible, and the image feels built for the platform instead of dragged in from a blog CMS. If you're tightening your broader visual system across channels, this guide for brands mastering social media content is a useful companion because it frames image choices as part of a repeatable content operation, not a one-off design task.
Timing doesn't fix a bad preview
Publishing at a better time can help distribution, but it won't rescue a poor visual. If the preview looks soft or the focal point is cropped, the article starts at a disadvantage. Pair image accuracy with strong timing by reviewing this breakdown of the best time to post on LinkedIn.
Quick Reference Guide to LinkedIn Article Image Sizes
Here are the specs you need for LinkedIn article images.
The main point to keep straight is simple: the feature image is the one people see in the feed, while the article cover image sits at the top of the article itself. Teams mix these up all the time, then wonder why a header that looks polished inside the article delivers a weak, cramped preview in the feed. That mistake costs clicks.
LinkedIn Article Image Specifications 2026
| Image Type | Dimensions (Pixels) | Aspect Ratio | File Types | Max Size |
|---|---|---|---|---|
| Feature Image | 1200 x 644 | 1.91:1 | JPG, PNG, static GIF | Keep the file compressed enough to load cleanly and stay sharp in feed previews |
| Article Cover Image | 1920 x 1080 | 16:9 | JPG, PNG, static GIF | Keep the file optimized so the header loads fast and does not get softened by heavy compression |
| Inline Images | No strict published article-specific dimension in the verified data. Use a consistent export size for visual continuity. | Flexible | PNG, JPEG work well in practice | Keep optimized for web and loading speed |
A quick rule I use with clients: if the image is meant to win the click, build for the feature image spec first. If it is meant to support reading after the click, build for the cover image spec. Using one file for both placements is possible, but it usually forces a compromise in cropping, text placement, or file weight.
What to remember if you're in a rush
- Feed preview asset: Build at 1200 x 644
- Header inside the article: Build at 1920 x 1080
- Text-heavy graphics: Default to PNG
- Photo-led graphics: JPEG is usually easier to keep lightweight
If your team repurposes creative across channels, keep a separate reference for vertical formats too. This quick guide to Instagram Story specs for repurposed social visuals is handy when an article graphic later gets adapted for Stories.
The easiest way to ruin a LinkedIn article image is to use the right file in the wrong placement.
The Feature Image Perfecting Your Feed Preview
You publish a strong article, share it in the feed, and it underperforms. A common reason is simple. The wrong image got optimized for the wrong job.
The feature image is the image people see before they click. It is not the same asset as the article cover image inside the article, and treating them as interchangeable usually hurts feed performance. In the feed, LinkedIn gives you a narrow window to signal quality, relevance, and clarity.
According to LinkedHelper's LinkedIn image size guide, the recommended feature image size is 1200 x 644 pixels at a 1.91:1 aspect ratio, and LinkedIn can display that preview at roughly 600 x 322 pixels in the featured section. The same reference notes that images under 1200 pixels wide can see a 30 to 50 percent drop in click-through rate, which matches our experience. Soft previews get ignored. Clear previews get clicked.
Build for the feed first
The feature image has one job. Earn the click in a crowded feed.
That changes how you should design it. A layout that looks polished as a large article header can fail once LinkedIn shrinks it. Small UI screenshots become illegible. Long headlines turn muddy. Fine lines and thin fonts disappear. I see this often when teams upload their 1920 x 1080 cover image as the feed image and assume LinkedIn will handle the rest. It uploads, but it does not preview well.
Use these rules for the feature image:
- Keep text short: A few words beat a full headline in a feed preview.
- Make the focal point obvious: Faces, bold shapes, and simple product visuals hold up better than busy scenes.
- Keep key elements away from the edges: Tight compositions often feel cramped after scaling.
- Use heavier type and stronger contrast: Feed previews punish subtle design choices.
The feature image sells the click. The cover image supports the reading experience after the click.
Where teams usually get this wrong
The confusion usually starts in production. A designer creates one polished header graphic and the marketing team reuses it for both placements. That saves time, but it forces a compromise between two different environments.
For the feed preview, I prioritize legibility at reduced size. For the article header, I can afford a wider, more atmospheric composition. If you use one file for both, the feed usually loses first, and that is the more expensive mistake because fewer people enter the article in the first place.
A quick check helps. Export the image, then view it at a much smaller size before uploading. If the message is unclear in two seconds, revise the layout, simplify the text, or swap the visual.
For teams repurposing article creative into native posts, this guide on how to format a LinkedIn post for feed readability is useful. The same rule applies in both places. Clear beats clever.
The Article Cover Header Mastering the In-Article Experience
A common production mistake hurts article performance twice. Teams design one polished image, use it as both the feed-facing feature image and the in-article cover header, then wonder why click-through rate softens even though the article itself looks strong.
The problem is simple. These two placements do different jobs. The feature image has to earn the click in a crowded feed. The article cover image takes over after the click and sets the tone for the page. If you confuse them, the feed usually pays the price first, and that is the more expensive loss.
The cover image has a different standard for success
Inside the article, the header image has more room to breathe. It can carry more atmosphere, more context, and a looser composition than the feature image. I still keep it disciplined. If the subject drifts too close to the top edge, the header starts to feel awkward on mobile. If the image depends on small text overlays, readability falls apart fast.
A strong cover header usually does three things well:
- sets the tone of the article without repeating the headline
- keeps the primary subject near the center area
- uses a clean composition that still feels balanced if LinkedIn crops it differently across devices
Feed image versus article cover
Here is the practical distinction:
| Image Type | Primary Purpose | What to optimize for |
|---|---|---|
| Feature Image | Get the click from the feed | Immediate clarity, strong contrast, fast recognition |
| Article Cover Image | Support the reading experience | Mood, context, balanced framing, cleaner top-of-page presentation |
That difference affects design choices more than teams expect. A wide cinematic header can look polished once the article opens, but it often loses force in the feed because the focal point feels distant. A tighter, text-led feature image can win the click, yet feel cramped and overly promotional as the article header.
How to design a cover header that survives LinkedIn cropping
LinkedIn does not display article headers exactly the same way on every screen. Safe composition matters more than decorative detail.
Use these checks before you upload:
- Keep faces, products, or key visual elements in the middle zone
- Treat the outer edges as flexible space, not as the place for important details
- Skip long text overlays. The article title already carries the headline load
- Preview the image on both desktop and mobile if your workflow allows it
- Reposition the crop if LinkedIn gives you that option
I use one simple rule during review. If the image only works when every edge stays visible, it is too fragile for an article header.
Teams that already build visual sequences for LinkedIn often get this faster after publishing a few LinkedIn carousel posts with image-based storytelling. The same principle applies here. Each frame or header needs a clear focal point, enough breathing room, and a layout that still works when the platform changes the crop.
What good cover headers usually look like in practice
The best article cover images are often less aggressive than the best feature images. They do not need to shout. They need to feel intentional.
Use a wider scene if the article benefits from context. Use a product close-up if the topic is specific. Use a branded graphic if your visual system is strong enough to carry the page without stuffing in extra copy. The test is whether the image makes the article feel more readable and more finished the moment the reader lands.
Best Practices for Inline Article Images
Inline images are where the article becomes easier to read. They break up long stretches of text, help explain a process, and give the page rhythm. Unlike the feature image or article cover, LinkedIn doesn't give you one rigid inline size in the verified data, so the goal is consistency.
I usually treat inline images as part of an editorial system. If one screenshot is wide, another is square, and a third is tiny, the article starts to look assembled rather than designed. Readers may not say that out loud, but they feel it.
Choose one visual logic and stick to it
You don't need every inline image to share the exact same crop, but they should feel related. That usually means deciding in advance what each image type is for.
A practical setup looks like this:
- Screenshots: Keep them large enough to read without zooming
- Charts or diagrams: Give them room and center them
- Illustrative photos: Use them sparingly so they don't interrupt the flow
- Branded graphics: Match font, spacing, and color treatment from image to image
Aspect ratio should follow the content
Flexibility offers an advantage. Some visuals need width. Others need height. The best inline image size depends more on what the image contains than on a universal rule.
Use the format that best suits the content:
- A dashboard screenshot often needs a wider crop.
- A step-by-step annotated graphic may benefit from more height.
- A quote card or pull-graphic should feel deliberate, not like filler.
If an inline image doesn't clarify, support, or pace the article, cut it.
Placement matters as much as size
A good inline image appears right when the reader needs it. Don't push all visuals to the top half of the article and leave the rest as uninterrupted text. Spread them where they reduce friction.
A few habits work well:
- Place screenshots immediately after the paragraph that references them.
- Use one stronger visual after a dense section to reset attention.
- Avoid stacking several decorative images with no explanatory role.
If you often turn long-form posts into swipeable assets later, this walkthrough on how to post a carousel on LinkedIn is a useful next step because many of the same visual clarity rules apply.
File Formats and Optimization for Fast Loading
A sharp image that loads poorly is still a bad asset. File format and export settings matter because LinkedIn compresses what you upload, and weak source files don't recover well.
LinkedIn article images have a maximum limit of 5MB per image for feed performance, accept PNG and JPEG, and should be exported at at least 72 DPI, according to HyperClapper's image size guide for LinkedIn posts. That same reference notes that PNG is better for text-heavy designs or logos, while JPEG is preferred for photo-heavy content.
Pick the format based on the content
This is the simplest decision rule I use:
| Format | Best For | Common Mistake |
|---|---|---|
| PNG | Text overlays, logos, screenshots, charts | Using PNG for large photos and ending up with a heavier file than necessary |
| JPEG | Photos, textured imagery, lifestyle headers | Using JPEG for small text and getting fuzzy edges |
If the image includes typography that needs to stay crisp, choose PNG first and compress from there. If it's a photographic header with no fine text detail, JPEG is usually the cleaner trade-off.
A practical optimization workflow
Many teams don't need a complicated process. They need a repeatable one.
- Export at the correct dimensions: Don't upload oversized files and hope LinkedIn sorts it out.
- Choose the right format first: PNG for graphics, JPEG for photos.
- Compress before upload: TinyPNG, Squoosh, Canva export settings, and Adobe Express all work.
- Preview on desktop and mobile: Compression problems often show up faster on phones.
For a broader technical overview of smart resizing and delivery, this guide to responsive image techniques is worth reviewing.
This short walkthrough is also useful if you want a visual explanation of image preparation before uploading:
Don't confuse DPI with visual quality on its own
People often obsess over DPI while ignoring dimensions and compression. For LinkedIn article image size, width, format, and file weight usually affect the result more directly than DPI alone.
Export for the screen you're publishing to, not for print habits you carried over from another workflow.
If you repurpose article visuals across channels, this guide on how to repurpose content helps build a cleaner system so you aren't resizing from scratch every time.
Troubleshooting Common LinkedIn Image Issues
Most LinkedIn image problems fall into three buckets. The image looks blurry, the crop feels wrong, or the file won't upload cleanly. Each has a direct fix.
Why your image looks blurry
Blur usually comes from one of three issues: the image is too small, the wrong format was used, or the source file was already weak before upload.
Try this checklist:
- Check the dimensions first: Your feed-facing article preview should use the proper feature image size, not a smaller substitute.
- Review the source asset: If the Canva, Photoshop, or Figma export already looks soft, LinkedIn will make it worse.
- Match format to content: Text-heavy graphics usually survive better as PNG than JPEG.
Why LinkedIn is cropping the image awkwardly
Cropping problems usually come from designing too close to the edges. If the important element sits high, low, or far to one side, different display contexts will expose that weakness.
A reliable fix looks like this:
- Rebuild the image with more empty space around the focal point.
- Move text and logos inward.
- Preview the image on both desktop and mobile before publishing.
- Use LinkedIn's repositioning option when available for article headers.
Why your file is getting rejected or feels slow
If the upload fails or drags, the file is often heavier than it needs to be, or exported in a format that doesn't suit the design.
Use this process:
- Compress the asset before upload
- Remove unnecessary resolution overhead
- Swap formats if needed
- Save a platform-specific version instead of reusing a web banner from another channel
The fastest fix is usually rebuilding, not patching
People waste time trying to salvage a bad image with tiny edits. If the composition is wrong, start over on the right canvas. It's faster than fighting a file that was designed for the wrong placement in the first place.
The cleanest publishing workflow is simple: one feature image built for the feed, one article cover built for the article, and a small set of inline image rules you follow every time.
If you want a faster way to schedule and publish polished social content without juggling tabs, exports, and posting windows, SleekPost is built for that. It gives creators and marketers a clean dashboard for planning, customizing, and publishing across platforms, including LinkedIn, so the work around your content doesn't take longer than the content itself.