Blog
How every part of this works
How every tool on this site works, what it will and will not do, and what happens to the files you upload. Written from the code rather than from a brief.
Start here
- What this site does, in one pageTen image tools, no account, nothing kept longer than two hours — and an honest list of what is not built yet.3 min read
- What happens to the images you uploadWhere your files go, exactly how long they stay, and why deletion is a property of the storage rather than a promise.3 min read
Every tool, explained
- How image compression works hereFour formats, four different encoders, and a rule that you never get back a file bigger than the one you sent.3 min read
- Resizing without wrecking the picturePercentages that land on exact numbers, vectors that stay vectors, and animations that still animate afterwards.5 min read
- What happens between the box you drag and the file you getThe editor draws on a preview; the cut is made on the original. Here is how the two are kept in step.4 min read
- Getting a JPG out of anythingFour decoders, a colour space that has to be corrected, and a transparency question only you can answer.4 min read
- Converting out of JPG, and turning a pile of them into an animationPNG, GIF or WebP from a single photograph — or one animated GIF assembled from the whole batch.4 min read
- The editor edits a document, not your photographNothing you drag is ever applied to the preview you are looking at — it is recorded, and replayed against the full-size original.5 min read
- Watermarking that lands in the same place on every imageText or a logo, sized as a share of the picture rather than in fixed pixels, so a batch of mixed sizes comes back consistent.3 min read
- Why the meme font is Bebas Neue and not ImpactA licensing decision, and the reason the preview in your browser matches the file you download exactly.3 min read
- Rotating a JPEG without re-encoding itQuarter turns and flips take a lossless path that rearranges the existing data instead of decoding and re-compressing.3 min read
- Screenshotting a web page without becoming an open proxyA real browser renders the page, and a guard decides what it is allowed to reach — the hardest part of this tool is the second half.3 min read
- How the background actually gets removedA segmentation model runs on our own server, works at 320 pixels, and never touches the resolution of your photo.5 min read
Under the bonnet
- What happens between pressing the button and the downloadA task, a queue, a worker and a signed URL — and why the work never happens inside the request that asked for it.4 min read
- Four ways an image file can attack a server, and what stops eachA file is not what its name says it is. Here is what is checked, in what order, and why byte limits catch none of it.4 min read