Skip to content

README: the 40 Mpx image ceiling #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tannevaled merged 1 commit into from
Nov 1, 2026
Merged

README: the 40 Mpx image ceiling #49

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,6 +162,15 @@ pixel as Chrome and WeasyPrint do; WeasyPrint's `--dpi` is the same lever. A
relative `src` resolves against `BaseURL`; an image that fails to fetch or
decode is left out.

**Images above 40 megapixels.** Since `go-gfx/gfx` v0.37.0 the codec refuses an
image of more than `codec.DefaultMaxPixels` (40 million pixels, width times
height) from its header, before allocating anything: the size comes from the
file, and a compressed format describes a huge image in a few bytes. The second,
full-size decode of an `<img>` described above is subject to it. Above the
ceiling it fails with `codec.ErrTooLarge`, and the embedded image is then the
engine's box-size bitmap instead of the full-size source (a source that
large is replaced, not dropped). There is no option to raise the ceiling here.

### Rendering with no network access

Stylesheets (`<link>`, `@import`) and `<img>` images are the only places
Expand Down
Loading