Enhancement: Investigate control over output PNG IDAT chunk size, might reduce file size of smaller palette-based images
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 32.7k
- Forks
- 1.4k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 5
Description
## Question about an existing feature
### What are you trying to achieve?
I have some PNG images. I want to use sharp to compress them and reduce file sizes.
I tried a few options. However, the output size (13.3KB) is always bigger than input size (11.4KB).
### When you searched for similar issues, what did you find that might be related?
### Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this question
https://github.com/retrobrainz/image-compress-test
### Please provide sample image(s) that help explain this question
See the repo above
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the standalone example repository linked in the issue and reproduce the comparison between the input and output PNG files. Investigate whether sharp exposes control over PNG IDAT chunk size and whether that could reduce the size of smaller palette-based images; done means documenting the finding or defining the needed enhancement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100