technologybriefs
Saved
Software · Tech history

JPEG

Joint Photographic Experts Group

JPEG trades irrevocable image data for universal compatibility—and still runs the web because nothing broke badly enough to force its replacement.

Worth your time?3.5/5Yes.Study the whole thing.What works, what does not, who it is for ↓
9:51in productionCh. 1 · It’s a codec, not a file/ 9:51 · ceiling 15 min
4 chapters · 9:51Ceiling 15:00

The brief is written and checked. The video joins this page when it is cut.4 chapters · 1 min read · 9:51 planned

Read the brief

JPEG is a 1992 DCT-based lossy compression standard. It delivers predictable 10:1 size reduction with acceptable visual trade-offs. It defines only the codec—not the file format. Its lossless mode is unused. It remains dominant not by superiority but by inertia.

SoftwareTech historyAlgorithmsComputingPhotographyAlgorithms across the network →
Chapters & takeaways4
  1. 1:00
    It’s a codec, not a file

    JPEG’s core mechanism is DCT-based lossy compression—not a file format, not a container, not a protocol.

  2. 2:43
    The number and the date are fixed

    10:1 compression was the target; 1992 was the year it shipped as ITU-T T.81 and later ISO/IEC 10918-1.

  3. 4:16
    What it omits matters as much as what it includes

    The standard specifies compression logic only—file packaging is external, and its lossless mode is ignored in practice.

  4. 5:57
    It’s a committee, not a corporation

    JPEG is a standards working group formed in 1986—not a company, not a product, not a brand.

Worth your time?

Yes. Study the whole thing.

3.5/ 5
What works
  • universal decode compatibility
  • hardware-accelerated encoding
  • predictable 10:1 compression
What does not
  • lossless fidelity
  • transparency support
  • animation
  • modern perceptual efficiency
Study it if
  • web developers
  • archivists handling legacy assets
  • embedded systems engineers
Skip it if
  • medical imaging specialists
  • print production professionals
  • AI training pipeline designers
The written brief1 min read

What it is and the problem it solves

JPEG is a lossy image compression standard created to reduce file sizes while preserving subjectively acceptable visual quality. It solves the problem of transmitting and storing photographic images over bandwidth- and storage-constrained systems.

How it works

JPEG uses the discrete cosine transform (DCT) algorithm to convert image blocks into frequency components. It discards high-frequency data deemed imperceptible, then quantises and entropy-encodes the remainder. The standard defines only this compression/decompression process—not how the data is stored in a file.

What works

It reliably achieves ~10:1 compression with perceptible but widely accepted quality loss. Its DCT-based codec is fast to encode and decode in hardware and software. It is universally supported across browsers, operating systems, and editing tools.

What does not

The lossless coding mode exists in the standard but is not widely supported. JPEG does not define a file format: JFIF and Exif do that separately. It does not guarantee consistent visual quality across devices or viewing conditions.

What it changes

JPEG established DCT-based lossy compression as the baseline for web and consumer imaging. It shifted image storage from raw or uncompressed formats to perceptually optimised bitstreams—enabling faster transmission and smaller archives at the cost of irreversible data loss.

Is it worth your time

Yes—if you need lightweight, interoperable image delivery where minor quality loss is acceptable. No—if you require lossless fidelity, transparency, animation, or modern perceptual efficiency. JPEG remains embedded in infrastructure, but it offers no new capability.

Same field · Software4 of 114
8:46
Arista Networks2004Arista Networks restructured the network operating system around process isolation and a central state database. Its value lies not in speed or scale alone—but in making failure local, upgrades safe, and debugging possible. It is a systems-level intervention, not a feature upgrade.
9:48
RedisSalvatore Sanfilippo · 2009Redis is an in-memory key-value database introduced in 2009 by Salvatore Sanfilippo to solve scalability issues at his startup LLOOGG. It delivers low-latency operations by holding all data in memory and using the fork system call to enable concurrent client service and disk persistence. It supports two persistence methods—RDB snapshotting and AOF journaling—with journaling introduced in version 1.1 and considered safer. Default configuration limits data loss to a few seconds upon full system failure. Redis supports master-replica replication with hierarchical trees and introduced clustering in April 2015 with version 3.0. It grew into one of the world’s most popular databases for caching, message brokering, and primary storage. In December 2024, Sanfilippo returned to Redis and implemented the Vector Set data structure for vector similarity search.
9:28
Texture mappingTexture mapping is the foundational technique that enabled efficient, artist-controlled surface detail in 3D graphics. Its 1974 debut by Edwin Catmull solved the problem of visual richness without geometric bloat—but introduced new problems in sampling accuracy, perspective distortion, and aliasing. It works reliably only when implemented as inverse, perspective-correct mapping. Everything else is either obsolete or broken.
9:28
ALGOL1959ALGOL is the first language to define scope, syntax, and semantics as interlocking formal systems—not as implementation conveniences. Its success was in writing, not execution. Its failure was in running.
Up next in Technology

JSON

Douglas Crockford · 2001 · 8:40

JSON succeeded not because it was novel, but because it refused to do anything except encode six values — and that restraint made it universal.

Next brief →Back to Software
8:40