Skip to content
FileBelow

Image tools

Fourteen tools, one engine. Each takes the requirement as its input rather than making you guess your way toward it, and every one runs on your own device — nothing is uploaded, and none of them needs an account.

It is the wrong size

A number from a form — kilobytes, or pixels — and a file that does not meet it.

It is the wrong shape

The right picture in the wrong frame. Cut it down, or add space around it.

It is the wrong kind of file

The destination will not take what your camera or your screenshot produced.

It needs to become something else

One file from several, a document from a photograph, a photograph you can publish.

Which tool do you need?

A form said your file is too big. Use the image compressor and type in the limit it gave you. If you are not sure what went wrong, start at my image is too large.

A form specified pixel dimensions. Use the image resizer. If the destination is a platform we have verified, its numbers are already filled in under sizes by platform.

You do not know which rule you are breaking. The requirement checker takes a destination and your file and tells you every rule that fails, before you spend another attempt finding out.

A form will not accept your file type. Use the image converter. If the file came off an iPhone it is almost certainly HEIC, and converting it to JPG is the fix.

The shape is wrong. Either crop it, which removes picture, or add a border, which adds space instead — which to choose depends on the photograph.

It is sideways. The rotate tool turns it a quarter at a time and writes the result into the pixels, so it looks the same everywhere.

What they have in common

Every one of these runs on your own device. There is no server on this site that could receive an image — it is entirely static — so nothing is uploaded, nothing is stored, and nothing is deleted later because nothing arrived. You can confirm it in your browser’s network tab, or by going offline after a page has loaded and using the tool anyway.

That is a property of the architecture rather than a promise, which is the reason it is worth stating — what FileBelow does with your files sets out exactly what that means and what it does not, and who maintains this covers the rest.

They also share one engine, which is why most of them can hit an exact file size limit as a side job. Adding a border, rotating, watermarking and merging all accept a maximum file size, and they apply it in the same pass rather than compressing afterwards — which matters, because two lossy saves cost more quality than one.