1Upload the JPG images that came out the wrong way round.
2Pick a quarter turn or a half turn, or type an arbitrary angle and choose a colour for the corners it will expose.
3Apply the rotation; the pixels and the orientation flag are reconciled so every viewer agrees on which way is up.
4Download the rotated JPG file.
Rotate JPG FAQ
Can I rotate a whole batch in one go?
+
Yes. The same rotation is applied across every file you upload, which is the practical fix for a folder of scans or camera output that all came in the wrong way round.
How does Rotate JPG turn the file?
+
Concretely, a rotation by a multiple of 90 degrees is done losslessly by transposing the DCT blocks — no re-encode, no generation loss; only an arbitrary angle needs resampling, because the pixel grid itself has to be rebuilt. Quarter turns and half turns are the common case and take the cheapest path available for the format.
Anything specific to JPG I should know?
+
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. It is the kind of thing that explains why a file looks right in one application and wrong in another.
Why does my file look correct on my phone but sideways elsewhere?
+
Because the orientation is stored as an EXIF flag rather than in the pixels, and not every viewer honours it. Rotating here normalises the two — the pixels and the flag end up agreeing, so the file looks the same everywhere.
What can I upload to Rotate 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 Rotate 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 Rotate 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 Rotate 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 Rotate 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. Rotate 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 Rotate 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 Rotate JPG means the conversion is made from the version you settled on, not from the one you were still fixing.
Is Rotate 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.
