Slides
Pick your images, put them in order, and download one PDF to upload to LinkedIn as a document post. The images never leave your browser.
Slides
One PDF whose pages are your images, in the order you arrange them. LinkedIn calls the result a document post; everyone else calls it a carousel. Upload the PDF through the document option in LinkedIn's composer and it becomes a swipeable deck in the feed.
X has no document post type — its composer takes up to four images per post, or a thread of images. A PDF gets you a downloadable file there and nothing else, so this tool is for LinkedIn only.
Nowhere. They are decoded, re-encoded and assembled into a PDF inside your browser. No image, or anything derived from one, is ever sent to a server.
Only your settings — page shape, fit, background colour and document
title — saved in your browser's localStorage under the key
oslikas-lcb-settings. Your images are never stored, and a
reload forgets them.
Yes, deliberately. Each slide is drawn to at most 1080 pixels wide and saved as a JPEG, which keeps a twenty-page deck around a few megabytes instead of tens. That re-encode also drops all EXIF metadata, including the GPS location some cameras record.
Your images are rarely the same shape as the page. Fill covers the page and crops the overflow, which is what looks best in the feed. Fit shows the whole image and pads the rest with the background colour. Either way the crop is taken from the centre.
A document post holds between 2 and 300 pages and at most 100 MB. LinkedIn recommends 1080×1350 (4:5) or 1080×1080 (1:1); pages of any other shape get cropped or padded by LinkedIn itself, which is what this tool exists to avoid.
Safari decodes HEIC and Chrome and Firefox do not, so it depends on your browser. Picking photos from an iPhone usually converts them to JPEG automatically; otherwise export them as JPEG first. The unreadable file is listed with a reason and the rest of the deck still builds.