jimp-dev/jimp

Larger (bytes) processed file than original

Open

#807 opened on Oct 21, 2019

View on GitHub
 (1 comment) (5 reactions) (0 assignees)JavaScript (785 forks)batch import
bugfile size issuehelp wanted

Repository metrics

Stars
 (13,218 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Expected Behavior

I expect the processed file size to be less than the original

Current Behavior

The processed file size is greater than the original

Failure Information (for bugs)

Even with .quality(75) and in some cases a smaller size then the original, the processed file is larger in bytes

jimp.read("src/path/to/image.jpg", (err, file) => {
    if (err) {
        console.log(err);
    } else {
        file.resize(400, jimp.AUTO)
            .quality(75)
            .write("public/path/to/image.jpg");
    }
});
  • Jimp Version: latest
  • Operating System: Mac
  • Node version: 12

Contributor guide

Research direction
Investigate the effect of the quality() method and the default save behavior in Jimp. Compare the encoding parameters for the input and output images. Check if the original image was already highly compressed and re encoding at a lower quality still results in a larger file due to re compression overhead.
Tech stack
javascriptnodejs
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Node.jsJimp
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70