LinkedIn banner maker

What this LinkedIn banner maker commits to

Every download from this page is 1584 pixels wide and 396 tall, or that shape doubled. Nothing here offers a height field, an aspect menu or a custom canvas, because the moment those exist the page stops being able to promise anything. The figure is LinkedIn’s recommendation for a profile background photo, taken from their help article on changing that photo and read on September 6, 2026, together with their file requirement of a JPG or PNG below 8 MB.

Company and showcase Pages take a different picture: 1512 by 256. Those proportions are nowhere near a profile background’s, so an export from here is the wrong artwork for a Page and no amount of rescaling repairs it. Hiding both behind a selector would bury the only choice worth making. The measurements for both, with their sources and the dates they were read, are collected in LinkedIn banner size.

Guides you set, because the platform states none

Competing editors draw a confident rectangle labeled “safe area”. Look for the specification behind it and there is nothing to find. What LinkedIn writes is that a cover may be adjusted for different screens, that adjusting can trim it either way, and that anything important belongs away from the borders. No coordinates, no margins, no breakpoints.

The dashed box in the editor is therefore adjustable and off until you ask for it. Widen or narrow it, put your wording inside, and read it as your own margin. It exists only in the browser: the encoder never sees it, so a downloaded file holds your artwork and lettering alone. Inventing coordinates would be actively harmful — it would persuade you to align a name against a boundary nobody has committed to, and layouts move.

How the picture is fitted

An incoming photograph is enlarged or reduced until it covers all four edges, then trimmed. Letterboxing would be the alternative and it is worse: bars baked into the upload are bars LinkedIn cannot strip. Which region survives is up to you — drag inside the frame, nudge with the arrow keys, or move the sliders. There are not two renderings to reconcile here. One routine draws the editor and the download, differing only in scale, so the frame is a literal rehearsal of the file.

Lettering sits above it in fonts already installed on your machine, sized by percentage of banner height instead of by pixel count. Doubling the export therefore doubles the type without you touching the control. Over a busy photograph, the shading switch drops an even veil across the whole banner so pale lettering survives without you editing the photograph itself.

Choosing between the two exports

1584 by 396 is what LinkedIn asks for and what you get by default. Selecting the larger option gives 3168 by 792 — identical proportions, four times the pixels. Because LinkedIn reduces oversized uploads itself, that reduction usually lands crisper on a dense display than rendering at the target count directly. Proportions are the thing that cannot be rescued afterwards; resolution can always be thrown away.

After each download the stub reports what the file measures and weighs, and flags a file that has reached LinkedIn’s 8 MB ceiling, since that ceiling turns an upload away instead of quietly resizing it. Flat fields and lettering survive PNG best; a photograph is normally far lighter as JPEG. Should a correctly proportioned banner still weigh too much, compressing it trades quality for bytes without touching its proportions, and image dimensions reports what any file measures before it goes anywhere.

Deliberate omissions

No gallery of ready-made designs appears here. Searches for banner templates want finished artwork by a designer, and dressing an empty canvas up as a template would only waste the visitor’s afternoon. Nor is there stock imagery, a mark library or a sign-in. What arrives is what leaves, wearing whatever words you added. To alter a banner you already have rather than compose one, the image resizer works to typed numbers, while making an image square solves the unrelated problem of a portrait photo.

No file reaches a server. Decoding, drawing and encoding all happen inside this tab, and the browser hands the finished image straight back to you; no route on this domain accepts an image at all. That is verifiable rather than merely asserted — watch the network panel while you work, or read the local-processing guide.