1Upload your JPG images and wait for the preview to appear.
2Drag out the region you want to keep, or lock the selection to 1:1, 4:3 or 16:9 and drag freely inside that ratio.
3Confirm the crop — the same rectangle is applied to every file you uploaded, which is how a set ends up genuinely consistent.
4Download the cropped JPG file, with everything outside the frame discarded.
Crop JPG FAQ
Can I crop several files to the same region at once?
+
Yes, and that is the case worth doing here rather than in an editor: the same rectangle is applied across the batch, which is how a set of product shots ends up genuinely consistent instead of approximately consistent.
How does Crop JPG select and cut the area?
+
Concretely, the crop is applied to the decoded image and the result is re-encoded, so it costs one generation; where the crop happens to land on 8-pixel MCU boundaries the encoder can keep the original blocks and the cost disappears. You drag the region you want directly on the preview, or type exact pixel coordinates if you already know them.
Anything specific to JPG worth knowing before I crop?
+
Yes — every save re-runs the quantiser, so repeatedly editing and resaving a JPG compounds generation loss even if you never lower the quality slider. That is the sort of detail that only shows up after you have overwritten the original.
What is the most common mistake when cropping JPG images?
+
Cropping before resizing. Crop first from the full-resolution original, then resize the result — doing it the other way round means the region you keep has already lost detail it did not need to lose.
What can I upload to Crop JPG?
+
Anything in the lossy raster family — JPG, JPEG, JFIF and WebP — plus the lossless formats (PNG, BMP, TIFF) if you want to mix them in one batch. The format is read from the file header, not the extension, so a photo saved with the wrong suffix still goes through.
Is there a file size limit on Crop JPG?
+
Yes: free accounts process images up to 25 MB each, which covers essentially every camera JPG and phone photo; the work is done by libjpeg-turbo and libwebp, the same libraries a desktop editor links against. Larger files are the one thing the free tier will stop you on, and the limit is per file rather than per batch.
Will Crop JPG lower the quality of my JPG images?
+
A lossy source is already the result of one quantisation pass, and any operation that has to re-encode adds a second. Where the job can be done without touching the pixel data we do that instead, and where it cannot you choose the quality factor yourself rather than getting a fixed default.
Can I run Crop JPG on several JPG images at once?
+
Yes. Drop the whole set into the upload area and they queue in parallel with identical settings — that is the main reason to do this in a browser rather than one file at a time in an editor. Free accounts run one file per batch; a pass lifts that.
Why does a EPUB site host Crop JPG?
+
EPUB.to is built around the open eBook format — XHTML in a zip, reflowable by design, and readable on hardware nobody has thought about the layout for. A book is a zip full of markup, images and fonts, so almost every job people bring to an eBook site is really a job on one of those things. Crop JPG runs on the same upload and the same account as the conversions because that is where it is needed.
What should I do with the result once Crop JPG is finished?
+
The converter on this site moves books between EPUB, MOBI, AZW3, PDF and DOCX, so a title ends up on whatever hardware is actually going to read it. Doing that after Crop JPG means the conversion is made from the version you settled on, not from the one you were still fixing.
Is Crop JPG here the same tool the sibling sites run?
+
The engines are shared — the same toolchain, the same workers, the same limits. What a EPUB site adds is a view on reflow: which of these operations a reflowable book genuinely supports, and which ones only make sense on the fixed-layout media inside it. It also starts from one fact about the format this site is named after: the book is a zip of XHTML with a manifest, so the text costs almost nothing and every decision that matters is about the embedded images and font subsets.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploads are deleted from the workers shortly after the job finishes, nothing is read and nothing is indexed. Free accounts exist for history and batch size, not for access.
