Features
Shrinkly takes the file you drop on it and hands back one that is easier to publish: compressed, or converted into the format your site needs — the same picture, in the container your page can use.
Compression and conversion answer two different problems: a file that is heavier than it needs to be, and a file in a format the page cannot use. Both work on how the file is stored; neither moves a pixel.
A camera or a design tool saves more detail than a page can show. Compression rewrites the file so it carries only what a browser needs in order to draw the picture: repeated patterns in the pixel data are packed tighter, and the parts of the file a page never displays are dropped. The picture keeps its proportions and its place in the layout; what changes is how much data has to travel to show it.
The same picture in a file that is never larger than the one you dropped.
A photograph, a screenshot of sharp text and a logo on a transparent background are not best served by the same encoding. Conversion takes the image you have and writes it in another format, so the same picture arrives in a container that suits the page, the content management system or the build step that receives it.
One picture in the format your page needs, without opening an editor.
The pixel width and height, and the proportions between them, stay exactly as they arrived. Nothing is cropped, stretched or scaled: the file is rewritten around the picture rather than the picture being redrawn smaller. The layout still decides how large the image appears on screen, and it now decides that for a picture carrying fewer bytes.
The same picture in the same place, so nothing on the page shifts.
Shrinkly opens PNG, JPEG, WebP, AVIF files and writes an image back in one of the other three formats. Writing a format is the browser’s own work, so Shrinkly offers the ones your browser can produce — each row below says what that format is for, and whether this browser writes it. Start with the format you have:
Converting changes how the picture is stored, not the picture itself: the image keeps its pixel dimensions and the proportions between them, and is written back out in a different container. Where a browser cannot write a format, Shrinkly does not offer it and leaves the file as it is.
Shrinkly opens the file, re-encodes it and offers it back to you from inside the page. There is no upload to wait for, no library of your images waiting on a server, and no account to create before the first file.
The image you choose. It is read, rewritten and handed straight to your downloads without a copy being kept for you to tidy up afterwards.
Those are the two facts Shrinkly’s backend keeps for the session: the kind is what the per-session count is kept by, and the byte count is what the size ceiling is checked against. The size recorded is the file you dropped, never the size of the smaller file that comes back, and neither fact can be turned back into a picture.
No account is needed to start: Shrinkly counts what this visit uses as it goes and shows the count here. These are the limits in force for your files right now, and the plan they belong to.
Shrinkly could not read the limits in force for this visit just now.