Skip to content

Browser Support

Dus Mamud edited this page Nov 9, 2026 · 1 revision

Browser Support

Every package's browser spec runs on CI in Chromium, Firefox and WebKit (Playwright) — the 1.0.x releases are green on all three engines. The table below summarises what that means per browser.

Capability Chrome / Edge Firefox Safari
Core + canvas formats (JPEG/PNG/WebP) Supported Supported Supported (16.4+ for the worker path)
WASM codecs Supported Supported Supported
HEIC decode WASM fallback WASM fallback Native (17+), WASM elsewhere

Good to know

  • Safari 16.4+ is the floor for the worker-based paths; the core canvas engine itself works on any browser with createImageBitmap and canvas convertToBlob.
  • No COOP/COEP required. All WASM builds are single-threaded, so the library embeds in any page or iframe without Cross-Origin-Opener-Policy / Cross-Origin-Embedder-Policy headers and without SharedArrayBuffer (ADR-0006).
  • HEIC decode is native-first: on Safari 17+ the browser's own decoder handles it; elsewhere the bundled WASM decoder (libheif + libde265) takes over — same API either way.
  • SVG input is rendered through an <img> element internally — createImageBitmap rejects SVG blobs in all three engines, so the packages route around it.
  • Workers: Chromium cannot start module workers from blob: URLs on opaque-origin pages — @dusrel/image-batch's worker pool accepts type: 'classic' for exactly that case.

Proof

  • CI browser matrix: Chromium · Firefox · WebKit on every release.
  • The consumer test runs 25 in-browser checks against the published packages in a real browser — including every codec roundtrip and a full process studio.

Full matrix and quirk log: dusmamud.github.io/dusrel-image/guide/browser-support

Clone this wiki locally