1Upload the JFIF images you want to work on; the file opens on an editable canvas in your browser with nothing installed.
2Crop, rotate, resize, draw, add text and shapes, or adjust colour — every change lands on a working copy, never on your upload.
3Preview the result at full size before you commit to it.
4Export back to JFIF, or to a lossless format instead if you are still part-way through editing.
JFIF Editor FAQ
Is my file uploaded, or does editing happen locally?
+
Editing happens in your browser; the file goes to our workers only for the operations that genuinely need server-side processing, and it is deleted shortly afterwards.
How does JFIF Editor let me edit without installing anything?
+
Concretely, the JPEG is decoded once into an RGB canvas, every change you make lands on that canvas rather than on the file, and the quantiser runs exactly once when you export — which is why editing here does not compound generation loss the way ten edit-and-resave cycles in a desktop app do. The editing surface is the browser, so there is nothing to install and no licence to hold.
Anything specific to JFIF in the editor?
+
Yes — many editors silently rewrite a JFIF as an ordinary JPEG on save, so keep the original if the .jfif extension itself matters to whatever consumes the file. Worth knowing before you export over your only copy.
Is anything lost when I export?
+
Only what the export format cannot represent. Choose a lossless output while you are still iterating and a compressed one when you are finished — exporting to a lossy format between edit sessions is what accumulates damage.
What can I upload to JFIF Editor?
+
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 JFIF Editor?
+
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 JFIF Editor lower the quality of my JFIF 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 JFIF Editor on several JFIF 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 JFIF Editor?
+
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. JFIF Editor 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 JFIF Editor 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 JFIF Editor means the conversion is made from the version you settled on, not from the one you were still fixing.
Is JFIF Editor 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.
