LinkedIn

Make your LinkedIn image glow in real HDR

Encode your logo or post image as HDR so its brightest pixels can render above the feed’s normal white on supported displays. Not a filter, and not an animation.

  • Exports a JPEG carrying a Rec.2100 PQ ICC profile — the route that survives LinkedIn’s re-encoding
  • Automatic white detection, or pick any brand colour
  • Free, no account, and processed entirely in your browser

This is a free online LinkedIn logo glow tool. It exports a JPEG carrying a Rec.2100 PQ ICC profile at the exact dimensions LinkedIn serves — 400 × 400 for a company logo or personal profile, 1200 × 627 for a post or ad creative, 4200 × 700 for a company cover. Matching those sizes matters because LinkedIn re-encodes every upload at quality 90 with 4:4:4 chroma, and a file it has no reason to resize comes through that pass almost untouched. The ICC profile is passed through unchanged, which is what carries the glow. Free, with no account.

LinkedIn compatibility last verified 28 August 2026.

No image?Try one of these:

Free, with no account and no watermark. Your image is processed in your browser and never uploaded — read how HDR glow works.

How to make a LinkedIn image glow

  1. 1Upload your logo or post image above. Nothing is sent to a server.
  2. 2The white regions are detected automatically. If your brand colour should glow instead, pick it from the palette or sample it with the eyedropper.
  3. 3Set the strength. Around 1,000–1,600 nits reads as clearly bright without looking blown out in a feed.
  4. 4Export with the LinkedIn preset. You get a JPEG with a Rec.2100 PQ ICC profile attached.
  5. 5Upload that exact file to LinkedIn. Do not open and re-save it in another editor first.

Why it works

Ordinary interface white sits at about 203 nits — that is the reference level the operating system paints the feed with. An HDR display can go several times brighter than that, but only when something tells it to. A Rec.2100 PQ file does exactly that: its pixel values are absolute luminance instructions, not relative brightness.

So a logo encoded at 1,600 nits sits beside interface white that stops at 203, and the difference is roughly three stops. Nothing was added to the artwork — the display is simply being asked for light it always had available.

What survives LinkedIn’s processing

LinkedIn re-encodes uploads to JPEG. That matters, because the two ways of signalling HDR do not survive it equally.

ICC profile on a JPEGSurvivesThe route this tool uses for the LinkedIn preset.
PNG cICP chunkStrippedExcellent for a page you host yourself, useless once LinkedIn re-encodes it.
Gain map / Ultra HDRNot preservedWorks well on Android and Google Photos; not on this path today.
Screenshot of an HDR imageLoses everythingCaptured as SDR, so the luminance is discarded.

This is observed platform behaviour, not a published guarantee. Last verified 28 August 2026.

What breaks the glow

  • Opening the export in another editor and saving it again — the profile is usually dropped.
  • Cropping or resizing after export. Re-render from the original instead.
  • Uploading a screenshot of the result rather than the exported file.
  • Letting a scheduling tool re-compress the image before it reaches LinkedIn.
  • Personal profile photos, which are re-processed more aggressively than company-page logos.

Best image types for this

The effect is strongest on flat, high-contrast artwork and weakest on photographs. That is a property of 8-bit PQ rather than a limitation of the tool: at the top of the PQ curve adjacent code values are far apart in luminance, so a smooth gradient bands where a solid shape does not.

Works very well

  • White or light wordmarks on a dark field
  • Flat vector logos and icons
  • Bold headline text
  • Solid brand colours with hard edges

Needs more care

  • Photographs with large smooth skies
  • Soft glows and gradients already in the artwork
  • Very low-contrast designs
  • Anything where more than about a third of the frame would glow

Who can actually see it

Roughly half of a typical feed audience. Anyone on a recent iPhone, iPad, MacBook Pro or a modern Android OLED will see it clearly. Anyone on an ordinary SDR monitor, or on Windows with HDR switched off, sees a normal image — the post still works, it just does not shine.

Because of that split, the image should read well without the glow. Treat the HDR as an enhancement for the people whose screens can show it, not as the thing carrying the design.

Check whether your display shows HDR

Questions

Does the glow work in LinkedIn ads?

Sponsored content goes through a different processing path than an organic post, and we have not verified it end to end. Treat organic posts and company-page logos as the tested route, and test an ad creative yourself before committing budget to it.

Why does it look normal on my colleague’s laptop?

Their display has no HDR headroom, or HDR is switched off in the operating system. The file is unchanged — there is simply nothing above white for it to use. Around half of a typical feed audience will see it flat.

Does the effect survive if someone screenshots my post?

No. A screenshot is captured and saved as SDR, which discards the luminance. This is why the effect cannot be demonstrated with a screenshot and has to be seen on the file itself.

Can I use a transparent PNG?

Yes, but LinkedIn delivers JPEG, and JPEG has no alpha channel. Transparent areas are composited onto a background you choose — black or white — before export.

Will LinkedIn ban this?

It is a standards-compliant image file, not an exploit: Rec.2100 PQ is an ITU broadcast standard and the file contains no script or animation. That said, platform image processing changes without notice, and an effect that relies on metadata surviving a re-encode can stop working at any time.

What are the numbers?

Every figure below is either a published constant or a value this tool computes. None is an estimate, and each one is traceable to the standard beside it.

Reference values for HDR glow encoding, with their sources
MeasurementValueSource
Diffuse white reference203 nitsITU-R BT.2408
PQ maximum10,000 nitsSMPTE ST 2084
8-bit PQ code for diffuse white148Computed
8-bit PQ code for 1,600 nits205Computed
Rec.2020 white ceiling10,000 nitsComputed
Rec.2020 green ceiling6,780 nitsComputed
Rec.2020 red ceiling2,627 nitsComputed
Rec.2020 blue ceiling593 nitsComputed
Blue's share of Rec.2020 luminanceabout 6%Computed
LinkedIn logo size400 × 400 pxMeasured
LinkedIn post and ad size1200 × 627 pxMeasured
LinkedIn JPEG re-encodequality 90, 4:4:4Measured
PriceFree, no accountThis site

Where do these figures come from?

This tool implements published standards rather than an in-house approximation of them. Each specification below defines part of what the exported files contain.

  • ITU-R BT.2100

    Defines the HDR system this tool encodes into — BT.2020 primaries with the PQ transfer function.

  • ITU-R BT.2408

    Sets diffuse white at 203 nits, which is the reference every brightness figure here is measured against.

  • SMPTE ST 2084

    The PQ transfer function itself: absolute luminance from 0 to 10,000 cd/m², independent of display.

  • ITU-T H.273

    The code points behind cICP 9 16 0 1 — colour primaries, transfer characteristics, matrix and range.

  • W3C PNG Third Edition

    Specifies the PNG cICP chunk, which is how an HDR PNG declares itself without an ICC profile.