JPEG has been around since 1992, created by the Joint Photographic Experts Group — old enough that most people use it daily without ever deciding to. This guide covers what the format actually does, where it wins, and the moments when it quietly costs you megabytes.
What JPEG actually is
JPEG stands for Joint Photographic Experts Group. It is a lossy format built for photographs, social media, web images.
The traits that matter day to day: transparency is not supported, animation is not part of the format, and software support in 2026 means every browser and device made in the last 25 years.
On disk, the honest expectation: a 12-megapixel photo lands around 3-4 MB at quality 85.
When JPEG is the right call
Reach for JPEG when the job is photographs, social media, web images — that is the territory the format was designed for, and where small file size, universal support, great for photos pay off.
The format's age is a feature here: decades of tooling means nothing in your pipeline will choke on it.
When to use something else
The weak points — lossy compression, no transparency, quality degrades on re-saving — are real. For modern web delivery, WebP and AVIF compress dramatically harder; for maximum-compatibility sharing, JPEG still opens everywhere; for crisp graphics with transparency, PNG remains the default.
Converting out of JPEG takes seconds in the browser — pick the target format on the converter and check the size difference yourself.
Desktop alternatives exist for every step — Photoshop exports all of these, Squoosh tunes compression visually, TinyPNG squeezes the last kilobytes — but they all process one file at a time, which is the bottleneck on real libraries.
How the compression actually works
Lossy compression throws away detail the eye is bad at noticing — fine texture, subtle color steps — and keeps what perception cares about. That is how a photo drops 80% of its weight while looking identical at arm's length; it is also why each re-save discards a little more.
Every recommendation here is downstream of those mechanics — formats do not have personalities, only algorithms.
How to open JPEG files
Before converting just to open a file, check the native options: most systems already handle JPEG.
Windows: the built-in Photos app handles common cases; GIMP and IrfanView are the free heavyweights, Photoshop the paid standard. If a JPEG file refuses to open, the viewer — not the file — is usually the limitation.
macOS: Preview opens it natively, Quick Look previews it from Finder, and Affinity Photo or Pixelmator cover serious editing without an Adobe subscription.
Linux and everything else: GIMP and ImageMagick do the whole job from desktop or command line. And in a pinch, a browser converter doubles as a universal viewer: upload, convert to PNG or JPEG, open anywhere.
Getting files in and out of JPEG
Out of JPEG — for sharing, uploading or shrinking: drop the file on the converter, pick a universal target like JPEG or PNG, download. Dimensions stay identical; only the encoding changes.
Into JPEG — when a workflow or platform demands it: the JPEG converter accepts whatever you have and hands back the format the destination asked for.
Either direction takes seconds per file; the slow part of any conversion job is deciding, not converting.
How JPEG ended up everywhere
the Joint Photographic Experts Group shipped the format in 1992. Formats from that period were built around very different constraints — dial-up bandwidth, smaller screens, simpler pipelines — and JPEG carries that DNA.
Decades later, the ecosystem around it is the real asset — almost every editor, library and operating system has battle-tested JPEG support.
JPEG next to the usual suspects
| Format | Compression | Transparency | Animation | Support (2026) |
|---|---|---|---|---|
| JPEG | Lossy | No | No | every browser and device made in the last 25 years |
| PNG | Lossless | Yes | No | every browser since the early 2000s |
| WebP | Lossy and lossless | Yes | Yes | over 96% of browsers in use in 2026 (caniuse) |
Keep this table in mind whenever an upload form forces a choice — the support column usually decides.
JPEG in real workflows
Follow a JPEG file through a normal week and you find it exactly where the spec predicts: photographs, social media, web images. The format persists there because the alternatives give something up that those workflows need.
The friction shows up between tools, not inside them: lossy compression, no transparency, quality degrades on re-saving only becomes a real cost when the file needs to travel.
That is the honest shape of most format decisions in 2026: not better or worse, but native habitat versus the open road.
What this means for page speed
Images are usually the heaviest asset class on a page, so format choice flows straight into Largest Contentful Paint — the Core Web Vitals metric Google weighs for ranking. Lighter images, earlier paint, better scores: the chain is that direct.
The compounding is what surprises people: 200 KB saved per image across a forty-image page is eight megabytes a visitor never downloads.
Measure before and after with PageSpeed Insights — the image-weight line item makes the improvement concrete instead of theoretical.
Troubleshooting the usual suspects
Colors shifted. Usually a color-profile story: the source carried a wide-gamut profile and the viewer assumes sRGB. Convert from an sRGB master when the destination is the web, and the shift disappears.
The file will not open. Nine times out of ten the viewer is the limitation, not the file. Try a second viewer before blaming the conversion, or convert to PNG — if that copy opens, the original was fine all along.
Transparent areas turned white. The target format has no alpha channel; flattening is the documented behaviour, not a bug. Re-convert to PNG or WebP if transparency must survive.
The file got bigger. Some content genuinely compresses worse in the new format — flat graphics in photo-oriented codecs, photos in graphics-oriented ones. The size readout before download is the early warning.
The metadata question nobody asks
Every photo from a camera or phone carries hidden baggage: capture date, device model, exposure settings and — on phones — often GPS coordinates. Conversion is one of the moments where that baggage can be kept or dropped.
Photographers archiving work want the opposite — capture data is part of the record — so they convert copies for sharing and keep JPEG originals untouched.
The practical rule: treat the original as the metadata archive and the converted copy as the public version. That division of labour answers most privacy and copyright questions before they come up.
JPEG myths, corrected
"Newer formats make JPEG obsolete." Formats retire when their niche disappears, not when something newer ships — and the niche here (photographs, social media, web images) is still very much alive in 2026.
"Converting always loses quality." Only lossy targets discard data, and only once per conversion. A single, sensible conversion is not the enemy; repeated re-saving through lossy formats is.
"Bigger file means better image." Past the point where compression artifacts vanish, extra kilobytes buy nothing visible. Size is a cost, not a quality score.
Will this file open in 2040?
Longevity favors formats with open documentation and a huge installed base — by that test, JPEG (around since 1992) is a reasonable bet. The bigger archival risks are storage media and missing backups, not the format dying.
A pragmatic archive policy: keep originals untouched, store a second copy on different hardware or cloud, and re-verify a sample yearly. The format question solves itself if the bytes survive.
The short version
JPEG is built for photographs, social media, web images, and there it remains hard to beat. Its real costs are lossy compression, no transparency, quality degrades on re-saving — felt mainly when files travel. Inside its habitat, keep it; at the border, convert deliberately and keep the original.
The disk-space angle
Translate the spec into hardware: a 12-megapixel photo lands around 3-4 MB at quality 85. Multiply by a real library — a year of projects, a phone's camera roll — and the format choice becomes a storage line item, not an abstraction.
Cloud plans make the same point in currency: the gap between formats is often the gap between the free tier and the paid one.
When the math turns uncomfortable, the fix is one batch conversion away — convert a sample folder first and project the savings from real output sizes.
Where people take JPEG files next
The traffic out of this format is predictable; the busiest routes are HEIC to JPEG, WebP to JPEG, PNG to JPEG.
Each route exists for one of the reasons covered above — support, size or features — and each takes the same three steps: upload, pick the target, download.
Serving JPEG to browsers
Browser reality first: every browser and device made in the last 25 years. That single sentence decides whether JPEG files get embedded directly in pages or converted before upload.
CMS platforms blur this line by converting uploads themselves — convenient, but you keep more control over quality by converting deliberately before the upload form.
Quality settings, demystified
Export dialogs put a number on compression, and the number means different things by family. For lossy output, the 80-85 zone is the working sweet spot: visually identical to maximum for most content, at roughly half the bytes.
For lossless output, the slider is a speed dial, not a quality dial — higher effort means slower encoding and smaller files, with pixels identical either way. Cranking it costs only patience.
Vector exports trade in precision instead: decimal places and curve simplification. The visible threshold sits far below where most tools default, which is why aggressive simplification rarely shows.
The reliable method beats every rule of thumb: export one busy image at three settings, view them at 100% zoom side by side, and pick the cheapest one you cannot tell apart. Two minutes, settled forever for that content type.
Write the winning setting into your project notes; future exports inherit the decision instead of re-litigating it.
Frequently Asked Questions
Is JPEG free to use?
Yes. JPEG can be created, opened and shared without licensing fees. The format dates back to 1992 and any patents relevant at launch have long stopped being an obstacle for everyday use.
What is a JPEG file used for today?
Mostly photographs, social media, web images. That is the niche where its strengths — small file size, universal support, great for photos — actually matter, and where you will keep meeting the format in 2026.
How do I convert a JPEG file?
Upload it to the converter, pick the target format and download the result. The whole round trip takes well under a minute, and batches come back as a single ZIP.
Why is my JPEG file so large?
Because of how the format stores data: a 12-megapixel photo lands around 3-4 MB at quality 85. If size is the problem, converting to a format with stronger compression is the direct fix — test one file and compare the readout.
Does JPEG support transparency?
No — JPEG has no alpha channel. If you need transparent areas, convert to PNG, WebP or AVIF, all of which support it.
Will browsers display JPEG?
Support in 2026: every browser and device made in the last 25 years. When a recipient or platform cannot handle it, converting to JPEG or PNG removes the question entirely.
How do I create a JPEG file in the first place?
Two routes: export directly from an editor that supports it (Photoshop, GIMP and Affinity all do for mainstream formats), or take any existing image and run it through a converter with JPEG as the target. The second route is faster when the source already exists.
Are JPEG and Joint Photographic Experts Group the same thing?
Yes — JPEG is simply the short name for Joint Photographic Experts Group. File extensions, MIME types and documentation use both interchangeably, which trips people up exactly once.
Can a JPEG file contain a virus?
An image is data, not a program — it does not execute. The realistic risk is a disguised executable wearing a fake image extension, so judge files by their source, keep the OS updated, and let the format worry about pixels.
What is the best way to email a JPEG file?
Check the size first: a 12-megapixel photo lands around 3-4 MB at quality 85. If the attachment pushes past a provider's limit (usually 20-25 MB), convert to a lighter format or share a link instead — recipients on slow connections will thank you either way.
Mini glossary
Alpha channel. The per-pixel transparency layer. Formats without one flatten transparent areas, usually onto white.
Lossy / lossless. Whether compression discards data permanently or packs it reversibly. The single most consequential word on any format's spec sheet.
Bit depth. How many shades each color channel can hold; higher depth means smoother gradients and bigger files.
Encoding. The act of writing pixels into a format's structure. Slow encoders (AVIF) trade time for smaller output.
Artifacts. Visible compression damage — blockiness, halos around edges — produced by aggressive lossy settings or repeated re-saves.
Color profile. Metadata describing which exact colors the numbers mean. Mismatched profiles are behind most "the colors changed" complaints.
Container. A file wrapper that can hold image data plus extras — depth maps, multiple frames — as HEIC does.
Rasterize. Converting vector shapes into fixed pixels; the one-way step that costs a logo its infinite sharpness.
Working with a JPEG file right now? Run it through the converter and compare the before/after sizes — two minutes of testing beats an hour of reading.
Written by Giovanni Picaro, a web developer who has been building image tools and optimizing sites since 2019. Sources: MDN image format reference and Google web.dev. Last reviewed: 2026.