[GH-ISSUE #740] Project file becomes larger #597

New issue

Open

opened 2026-02-26 09:32:01 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 09:32:01 +03:00

Owner

Originally created by @xiaomayidechuanshuo on GitHub (Oct 9, 2020).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/740

After making continuous jpg format pictures into gif, the exported project far exceeds the total size of the imported pictures. How can we ensure the smallest project file without reducing the number of frames? I found that the problem is that the file is converted Into png format, so the file is enlarged

Originally created by @xiaomayidechuanshuo on GitHub (Oct 9, 2020). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/740 After making continuous jpg format pictures into gif, the exported project far exceeds the total size of the imported pictures. How can we ensure the smallest project file without reducing the number of frames? I found that the problem is that the file is converted Into png format, so the file is enlarged

kerem commented

2026-02-26 09:32:01 +03:00

Author

Owner

@Gnbrkm41 commented on GitHub (Nov 8, 2020):

I think it's a compromise between quality and size; jpeg is a lossy format, which means when you compress the image you end up losing a bit of the original information in exchange for smaller sizes. While the loss is normally small enough to go unnoticed, you will start noticing compression artifacts that look like grains or weird noises if you repeatedly edit and re-compress the image. This makes it less suitable for things like project files, since normally you end up editing those multiple times.

You don't get such issues when using PNG since PNG is a lossless format, which means you get to preserve the original quality until you decide to encode the images into something lossy (like gifs).

In my opinion (Disclaimer: I do not contribute to the project), the project file format should remain as is for higher image quality.

@Gnbrkm41 commented on GitHub (Nov 8, 2020): I think it's a compromise between quality and size; jpeg is a lossy format, which means when you compress the image you end up losing a bit of the original information in exchange for smaller sizes. While the loss is normally small enough to go unnoticed, you will start noticing compression artifacts that look like grains or weird noises if you repeatedly edit and re-compress the image. This makes it less suitable for things like project files, since normally you end up editing those multiple times. You don't get such issues when using PNG since PNG is a lossless format, which means you get to preserve the original quality until you decide to encode the images into something lossy (like gifs). In my opinion (Disclaimer: I do not contribute to the project), the project file format should remain as is for higher image quality.