filename.heic
Queued—
LinkedIn's uploader stalls or refuses the photo you took at the conference. Convert it below and the post goes up with the image intact.
100% Local — Files Never Leave Your Device
Drop your photos here
or pick them from your device — for posts, articles and profile images
Supports .heic and .heif from iPhone, iPad and modern Android cameras
90% survives LinkedIn's own re-compression better than a lower setting.
filename.heic
Queued—
LinkedIn's web uploader accepts JPG, PNG and GIF and validates before anything is read, so a .heic is refused outright — usually with a vague error or a spinner that never finishes. The mobile app converts on the way out, which is why posting from a phone works and posting from a laptop does not.
The same applies to article headers, company page banners and profile photos, all of which run through the same upload validation.
LinkedIn re-compresses everything it displays, so uploading a very large file gains you nothing — but starting from a high-quality JPG means what survives their pipeline still looks sharp in feed and on retina screens.
Resolution is unchanged, so a photo intended as an article header is still wide enough for a full-width crop.
Drag them onto the box above or press Select Files. Conversion runs on your own device.
Download them, then attach in the post composer, article editor or profile as usual.
Your JPGs carry no EXIF metadata.
Conversion re-encodes pixels only, so capture dates, GPS coordinates and camera details are not carried across. That is usually what you want for anything published, but keep your original .heic files if those timestamps matter to you.
LinkedIn accepts JPG, PNG and GIF for posts, articles and profile images, and does not accept HEIC. Converting to JPG is the reliable route, and JPG is what LinkedIn's own image pipeline is built around.
The LinkedIn mobile app converts photos to JPEG as it uploads. The web uploader receives the original .heic and rejects it at validation. Converting first gives you the same result from any device.
No. The decoder is a WebAssembly module that runs inside your browser tab, so the photo is read from your device into memory and converted there. You can check it in your browser's Network tab, or disconnect from the internet once the page has loaded and convert anyway.