Skip to content

DEV Community

← All Trends

Browser Image Export & Compression Quirks

17 posts in this trend in the last 7 days • Active 23 minutes ago

yue xing

Sep 30

Browser JPEG quality has only 101 steps: 0.955 and 0.964 give the same file

#webdev #javascript

3 min read

AsyncMonk

Oct 1

My upload code turned every image into JPEG. Red posters got bigger

#webdev #javascript

4 min read

Oct 1

On a red poster, PNG-8 was smaller and cleaner than every JPEG

#webdev #javascript

5 min read

yue xing

Oct 1

Why Firefox's quality-0.9 JPEG is 56% bigger and cleaner on red text

#webdev #javascript

5 min read

Sep 30

toBlob('image/webp', 1.0) is lossless, and 3.5 bigger than 0.999

#webdev #javascript

3 min read

Lank_M

Oct 2

Progressive JPEG saved 4–6% of bytes and cost 2.5x decode time

#webdev #javascript

3 min read

hao jia

Oct 1

Why red text blurs in canvas JPEG exports, and where 4:4:4 kicks in

#webdev #javascript

5 min read

Lank_M

Oct 1

JPEG quality 75 at 4:4:4 beat 0.99 at 4:2:0 on red text

#webdev #javascript

5 min read

hao jia

Sep 30

Compress-to-size in the browser: probe the quality floor before you bisect

#webdev #javascript

4 min read

AsyncMonk

Sep 30

What a 200 KB upload limit costs a 24 MP photo: time, pixels, quality

#webdev #javascript

4 min read

hao jia

Oct 2

Decoding a progressive JPEG took 14 MiB more memory in my test

#webdev #javascript

3 min read

AsyncMonk

Oct 2

Browsers only export baseline JPEG, so progressive is a server job

#webdev #javascript

3 min read

Lank_M

Sep 30

Same 200 KB, three formats: why WebP and AVIF look cleaner than JPEG

#webdev #javascript

4 min read

yue xing

Oct 2

What a progressive JPEG shows with only 10% of its bytes

#webdev #javascript

3 min read

AsyncMonk

Oct 4

canvas.toBlob silently crops WebP past 16,383 px, and nothing tells you

#webdev #javascript

3 min read

yue xing

Oct 4

Creating a canvas costs nothing. Drawing a 16384 one costs 1 GiB

#webdev #javascript

4 min read

Oct 2

Progressive JPEG saved me 4–6% and cost 2.5x the decode time

#webdev #javascript

3 min read

Trend Analysis

Developers are deeply benchmarking client-side canvas image exports (JPEG, WebP, PNG) across browsers, uncovering surprising file size inflation, decoding performance costs, and quality anomalies like red text blurring. These empirical findings challenge long-standing rules of thumb regarding format selection and compression settings in web apps.

Core Questions Under Debate:

How do different browser engines handle JPEG chroma subsampling and quality parameters for high-contrast text?
What are the actual performance and file size trade-offs between progressive and baseline JPEGs on device?
Why does passing a quality of 1.0 to canvas.toBlob for WebP trigger a massive file size jump compared to 0.999?

First detected: October 01, 2026

Last updated: 23 minutes ago

Algorithm: Vector Leader Clustering (threshold: 82%)

About this trend

This trend groups posts from the last 7 days that discuss similar concepts, technologies, or ideas.