ilovejpg is a private, browser-based JPG editor that resizes, compresses, rotates and captions photographs, turns images into PDF and PDF pages into JPG, all on your own device, with no upload, no account and no watermark.
Resize, compress, rotate, adjust, caption and convert.
Processed on your device. Nothing is uploaded.Drag the text on the preview to position it.
Order the pages, pick A4, Letter or image size, then save.
Your PDF is written in the browser.ilovejpg is a browser-based workshop for JPEG photographs and the documents built from them. It brings together the tasks people perform most often with images, such as resizing for an application form, compressing for an email, rotating a sideways scan, adding a caption, converting between JPG, PNG and WebP, binding photographs into a PDF and extracting PDF pages as pictures, and it performs every one of them inside the web page itself.
That last point is the defining design decision. A conventional online converter sends your file to a remote server, processes it there and returns the result. ilovejpg reads the file into your browser's memory and processes it with the HTML5 Canvas API and JavaScript running on your own processor. The photograph never crosses the network, so there is nothing to intercept, retain or delete afterwards.
Privacy here is not a promise written into a policy; it follows from where the code runs. Files are processed on the device that opened them and nowhere else.
Every setting is visible and adjustable: exact pixel dimensions, a quality value from 1 to 100, and a target size in kilobytes when a form demands one.
Rather than hundreds of loosely related utilities, the toolkit concentrates on the jobs that JPG files and their PDF companions genuinely require.
Ten capabilities, each designed to do one job properly and to show you exactly what it will produce before you save.
Set quality on a scale from 1 to 100 and the projected file size is recalculated from a genuine encode of the full-resolution image, not an approximation. For most photographs, values between 80 and 90 remove the majority of the bytes in a camera original while leaving nothing a viewer could point to.
Quality 1–100Enter a limit such as 100 KB and the encoder searches for the highest quality that still fits beneath it.
Binary searchWork in pixels or percentages, with an aspect-ratio lock that prevents stretched faces and squashed text.
Up to 16,000 pxCorrect sideways scans and mirrored selfies in quarter turns, applied in the same pass as every other edit.
Lossless orderBrightness, contrast, saturation and grayscale, calculated with identical arithmetic in the preview and the export.
Per-pixelType a caption, choose its size and colour, add a contrast band, then drag it into place on the preview.
Drag to placeExport JPG for photographs, PNG for screenshots and sharp graphics, or WebP for compact web images.
JPG · PNG · WebPBind several images into one ordered PDF on A4, US Letter or image-sized pages, with a choice of orientation and margin. In the other direction, render every page of a PDF as a JPG at 72, 144 or 216 DPI and save pages individually or as a single ZIP archive.
Both directionsRe-encoding through the canvas leaves EXIF data behind, including GPS coordinates and device details.
Privacy by defaultRuns in any current browser on Windows, macOS, Linux, ChromeOS, Android and iOS.
Web standardsThree stages, every one of them carried out on your own device.
Choose or drop a JPG, PNG, WebP, GIF or BMP image, or a PDF for page extraction. The browser decodes it locally and honours the camera's orientation flag, so portraits appear upright.
Set dimensions, rotation, tone, text, format and quality. The preview redraws immediately, and the size estimate comes from a real encode of the full-resolution image.
The finished file is generated in memory and passed to your browser's download manager. Close the tab and the working copies disappear with it.
Different jobs demand different settings. These are the situations the toolkit handles most often, with the values that tend to work.
Application portals for universities, scholarships and employers routinely impose strict upload rules: a photograph under 100 KB, a signature at exact pixel dimensions, a transcript scanned to PDF. A rejected upload costs time at the worst possible moment. Resize the image to the requested dimensions first, then use the target-size field so that the encoder finds the best quality that still satisfies the limit. Certificates and transcripts can then be bound into a single PDF in the order the form expects.
Passport, visa and identity applications specify pixel dimensions, file weight and sometimes the background colour of the photograph. ilovejpg prepares the file precisely, setting exact dimensions and a high quality value so that facial detail survives. It does not judge whether a photograph meets an authority's rules, so always read the issuing body's specification and leave overlays and colour effects switched off.
Images are usually the heaviest part of a web page, and the largest image above the fold often determines how quickly a page appears to load. Resize photographs to roughly twice their displayed width for high-density screens, export at a quality between 80 and 85, and choose WebP where your platform supports it, keeping a JPG for older systems. Metadata disappears in the same step, trimming a few more kilobytes.
Marketplaces reward consistency. Product photographs taken on different days under different light look untidy side by side, and oversized files slow catalogue pages. Bring each image to the same square dimensions, lift brightness or contrast slightly where the lighting was flat, and export every listing photograph at the same quality so that the range looks deliberate.
Client proofs need to be quick to send, clearly marked and too small to print well. Reduce the long edge to around 2,048 pixels, add a discreet text overlay with your name, and export at a moderate quality. Your full-resolution originals never leave your archive, and the proofs carry no camera metadata revealing where a shoot took place.
Expense claims, lesson resources and reports constantly move between images and PDFs. Turn photographed receipts into one ordered PDF for a claim, or render the pages of a PDF handout as JPG images that can be placed on slides or shared in a messaging app where PDFs are inconvenient to preview.
Where it runs, and how it compares with the two usual alternatives for editing and converting images.
ilovejpg relies only on features that every current browser implements: the File API to read your files, the Canvas API to draw and adjust pixels, Blob objects to assemble downloads and Web Workers to render PDF pages without freezing the page. No extension, Flash component or desktop helper is involved, which is why the same tools behave identically on a work laptop, a school Chromebook and a phone.
Inputs: JPG, JPEG, PNG, WebP, GIF, BMP and PDF. Outputs: JPG, PNG, WebP, PDF and ZIP.
| Criterion | ilovejpg | Upload-based web converters | Installed desktop editors |
|---|---|---|---|
| Where files are processed | Your browser, on your device | A remote server | Your computer |
| Installation | None | None | Required, with updates |
| Account | Never | Often, for larger files | Sometimes, for a licence |
| Speed on small jobs | Immediate, no transfer | Limited by upload and download | Fast once the program is open |
| Images into one PDF | Yes | Usually | Varies by program |
| Layers, masks and RAW | No | Rarely | Yes, in fuller editors |
| Locked-down work computers | Runs in the browser | Runs in the browser | Often blocked by IT policy |
| Price | Nothing to pay | Limited free tiers | Free or paid |
Most problems with image files trace back to a small number of causes. These are the ones that occur most often, each with its remedy.
Cause. Most browsers cannot decode HEIC or camera RAW files, and a damaged download may be unreadable.
Fix. Export the photo as JPG first. On an iPhone, Settings › Camera › Formats › Most Compatible makes the camera save JPG in future.
Cause. The pixel dimensions are far larger than the destination needs.
Fix. Reduce width and height before lowering quality. Halving both dimensions removes three quarters of the pixels.
Cause. JPEG encodes sharp edges poorly at low quality settings.
Fix. Raise quality above 85, or export screenshots and text-heavy graphics as PNG.
Cause. Some software ignores the EXIF orientation flag that phones use.
Fix. Rotate in quarter turns and save. The new file stores the pixels upright, so no flag is required.
Cause. JPG has no transparency channel, so transparent pixels need a background.
Fix. Choose PNG or WebP output whenever transparency must survive.
Cause. High resolution on a long document asks a great deal of the device.
Fix. Use 144 DPI for screen use; reserve 216 DPI for print or fine detail.
Cause. The document is password-protected or damaged.
Fix. Open it in a PDF reader with the password, save a copy you are entitled to use, then try again.
Cause. The browser is blocking automatic or multiple downloads.
Fix. Allow downloads for this site, or use Download all to receive a single ZIP file.
Because nothing is installed, the requirements are simply those of a modern browser, plus enough memory for the size of image you work with.
A compressed JPG on disk is far smaller than the image it represents. Once decoded, every pixel occupies four bytes for red, green, blue and transparency, so a 24-megapixel photograph needs roughly 96 MB of memory, and editing briefly holds several copies at once.
On a modern computer this is trivial. On an older phone with little free memory, very large photographs may open slowly; reducing their dimensions in the first step keeps everything that follows quick.
The safest file transfer is the one that never happens. Here is what that means in practice.
Many people hesitate before placing a passport scan, a signed contract or a family photograph into an online tool, and they are right to. ilovejpg was designed so that the question of what happens to your file on someone else's server simply does not arise.
Files are read through the File API and processed in your browser's memory. They are never transmitted to this website or anyone else.
GPS coordinates, device details and timestamps stored as EXIF data are not carried into the files you save.
There is no login, no gallery and no stored history, so there is nothing to breach and nothing to forget to delete.
Open the Network panel in your browser's developer tools while you edit, and you will see no request carrying your image.
An honest assessment, so that you can judge whether it suits the job in front of you.
Straight answers about the toolkit, privacy, file formats, compression and conversion.
ilovejpg is a browser-based toolkit for JPG images and the PDF documents built from them. It resizes, compresses, rotates, flips, adjusts and captions photographs, converts between JPG, PNG and WebP, binds images into a PDF and renders PDF pages as JPG files, with every step carried out inside your own browser.
No. There is no price, no subscription, no daily quota and no watermark stamped on your results. Because the processing is done by your own device rather than by a server, each additional file costs the site nothing to handle, which is what makes an unrestricted service sustainable.
No. Files are read through your browser's File API and processed in memory with the Canvas API and JavaScript. The finished file is generated locally and handed straight to your downloads folder. You can confirm this by watching the Network panel of your browser's developer tools while you edit.
Yes. The tools run in current versions of Chrome, Safari, Firefox, Edge, Opera and Samsung Internet on Android, iPhone and iPad as well as on Windows, macOS, Linux and ChromeOS. Very large photographs may take a little longer on older phones because the work is done by the device itself.
No. ilovejpg is a separate project with its own code, design and ownership. It has no partnership, endorsement or commercial relationship with iLovePDF, iLoveIMG or their owners, and those names belong to their respective holders. Many visitors arrive having typed a similar phrase, which is why the question comes up.
Not directly. Converting a photographed page into editable Word text requires optical character recognition, which ilovejpg does not perform. What it can do is prepare the image for OCR: rotating it upright, increasing contrast, switching to grayscale and setting a sensible resolution, all of which improve recognition accuracy in the software you use next.
None at all. Both extensions describe exactly the same format. Early versions of Windows limited file extensions to three characters, so .jpeg was shortened to .jpg, and the two have coexisted ever since. Software treats them identically, and renaming one to the other changes nothing inside the file.
JPEG compression is lossy, so some information is always discarded when a file is encoded. The question is whether the loss is visible. For most photographs, quality settings between 80 and 90 produce files several times smaller than a camera original with no difference that a viewer would notice at normal size.
When you enter a limit in kilobytes, ilovejpg encodes the image repeatedly, halving the range of possible quality values each time, and keeps the highest quality whose file falls under your limit. If even the lowest quality is too large, it tells you so, because the remedy is to reduce the pixel dimensions instead.
This is generation loss. Each save quantises the image again and discards a little more detail, much as a photocopy of a photocopy degrades. Keep your original untouched, make every edit from it, and export to JPG once at the end. If you must edit repeatedly, work in PNG and convert last.
Use 72 DPI for quick previews and thumbnails, 144 DPI for sharp on-screen reading, slides and email, and 216 DPI when you need fine text, printing or later cropping. Each step up multiplies the pixel count, so a 216 DPI page has nine times the pixels of the same page at 72 DPI.
Yes. Smartphone JPGs often carry EXIF metadata including GPS coordinates, the device model and the time of capture. When ilovejpg exports an image, it writes only the pixels from the canvas, so that metadata is not carried into the new file. This makes it a sensible last step before sharing photographs publicly.