LinkedIn Photo Resizer — Profile 400×400 and Banner 1584×396

Use the available LinkedIn presets as a starting point and confirm current personal-profile and company-page requirements with LinkedIn before publishing.

Upload your image, pick the LinkedIn personal banner (1584 × 396) or company page cover (1128 × 191) preset, drag to position the focal point inside the safe area, then download. The safe area marker ensures the LinkedIn profile photo does not cover important text.

Keep the bottom-left quadrant (roughly 250 × 250 pixels) clear — that is where the profile circle sits on desktop. The editor shows a translucent overlay so you can position the focal point in the upper-right where it stays visible.

JPEG is best for photographic banners with people, offices or backgrounds — smaller files load faster on slow connections. PNG is better for banners with sharp text, logos and gradients where compression artifacts would be visible.

LinkedIn crops the banner differently on mobile and desktop. The editor previews both views so you can confirm critical text and faces stay inside the safe area on both, avoiding the common "banner cut in half" mistake on the mobile app.

Yes. Your image is uploaded over HTTPS, resized on our secure servers, and removed under our Security policy — we do not sell the file or share it with third parties, so unreleased campaign visuals, executive headshots and confidential brand assets stay protected. If your policy requires images to never leave your device, use an offline desktop image editor instead.

Cover fills the target frame completely, cropping any excess — best for banners you want edge-to-edge. Contain fits the whole photo inside the frame without cropping, filling any empty space with your chosen background color. Stretch forces the image to exactly match the target size, which can distort people or logos if the aspect ratio is very different from your source photo.

Switch Fit to Contain, then use the Background color picker to fill the letterbox area — it defaults to LinkedIn blue (#0a66c2) so a logo on a transparent or plain background blends in, but you can pick any hex color to match your own brand instead.

Personal banner (1584x396), company banner (1128x191), profile picture (400x400), company logo (300x300), square logo (60x60), post image (1200x627), article cover (1280x720) and event cover (1776x444) — pick the preset for the placement you're uploading to and the exact pixel dimensions are applied automatically.

Yes — the Format selector includes JPEG, PNG, WebP and AVIF. WebP and AVIF typically produce smaller files at the same visual quality, which helps if you're hosting the image yourself rather than uploading straight to LinkedIn, which still expects JPEG or PNG on upload.

The Quality slider (40-100%, shown for JPEG/WebP/AVIF) controls compression — 85-92% is a good default that keeps text and logos crisp while staying well under LinkedIn's upload limits. PNG output ignores the slider since PNG compression is always lossless.

LinkedIn displays profile pictures as a circle, so the square corners of any photo you upload get cropped away. When you pick the Profile picture (400×400) preset, a 'Show safe zone' button appears over the preview — turning it on dims the four corners LinkedIn will cut and outlines the circle it will actually show, so you can confirm your face or logo stays fully inside before downloading. Toggle it off any time to see the untouched square image.

Select the Profile picture preset, keep Fit set to Cover so the photo fills the circular frame without empty space, then switch on the safe zone overlay to see exactly which corners LinkedIn will cut away. Reposition or re-crop your source photo so your face sits inside the dashed circle before downloading — this catches the classic 'top of head cut off' mistake before it goes live on your profile.

LinkedIn post images look best at 1200×627 px — the same 1.91:1 ratio LinkedIn uses for shared-link previews. The resizer includes a Post image preset at exactly that size, plus an Article cover preset at 1280×720 for LinkedIn article headers. Pick the preset, choose cover or contain fit, and download an image the feed will not crop.

Yes — Pixoate supports batch and bulk processing. Switch to Batch mode, add up to 60 images on Premium or 200 on Pro, set your options once, and every image is processed with the same settings before you download a single ZIP. Bulk processing is a Premium feature; the output uses the same quality and settings as single mode.

Yes — with bulk processing you configure the settings a single time and they apply to every item in the batch — up to 60 images on Premium or 200 on Pro. There is no need to repeat the setup per item, and Temporary uploaded and generated files are processed securely and deleted automatically.

Almost always one of three things. The file is over the 11 MB free upload limit — Premium takes 50 MB and Pro 120 MB. The format is not one this tool accepts, so check the list shown on the upload panel. Or the file is not really the format its name says: renaming a file does not change what is inside it, and that is the reason a valid-looking image gets refused.

The right pixel size only controls the file. The platform still decides what part of it shows in a feed, a preview card, or a circular profile mask — and each surface crops differently. Keep faces, logos and text inside the middle 80% of the frame so nothing important sits where a crop can reach it, and check the preview inside the app before you publish.

No. You can run LinkedIn Image Resizer and download the free result without an account, and it carries no watermark. Premium is what you buy when the limits start to bite: up to 60 files in one batch, larger uploads, no daily cap, and the original-resolution result. Nothing is revealed at the download step that was not visible before you started.

No — LinkedIn Image Resizer runs in the browser on desktop and phone. There is nothing to install, no trial to start, and no license to buy before you can see whether it does what you need. Try it on the file you are actually stuck with rather than a sample.