starred/ScreenToGif

Fork 0

mirror of https://github.com/NickeManarin/ScreenToGif.git synced 2026-04-25 15:15:51 +03:00

[GH-ISSUE #383] Uses A Lot Of Resources #317

New issue

Closed

opened 2026-02-26 09:30:58 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 09:30:58 +03:00

Owner

Originally created by @GKid94 on GitHub (Oct 3, 2018).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/383

The software uses a lot of my CPU, RAM and Disk when it's loading the recorded GIF and when it's saving it and the GIF's size is really large

Originally created by @GKid94 on GitHub (Oct 3, 2018). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/383 The software uses a lot of my CPU, RAM and Disk when it's loading the recorded GIF and when it's saving it and the GIF's size is really large

kerem closed this issue

2026-02-26 09:30:58 +03:00

kerem commented

2026-02-26 09:30:59 +03:00

Author

Owner

@vatterspun commented on GitHub (Oct 6, 2018):

The software uses a lot of my CPU, RAM and Disk when it's loading the recorded GIF and when it's saving it and the GIF's size is really large

ScreenToGif on my Win7 machine is taking up 11 megs of RAM, which is below average for programs of its type. ShareX (which also generates screen recordings) for example takes up around 20 megs.

As far as output file size, those can definitely get out of hand quickly. Various tricks to reduce size are discussed in #299

If you need a very lightweight recorder, LiceCap uses considerably fewer resources but also has fewer features and no editor component.

@vatterspun commented on GitHub (Oct 6, 2018): > The software uses a lot of my CPU, RAM and Disk when it's loading the recorded GIF and when it's saving it and the GIF's size is really large ScreenToGif on my Win7 machine is taking up 11 megs of RAM, which is below average for programs of its type. ShareX (which also generates screen recordings) for example takes up around 20 megs. As far as output file size, those can definitely get out of hand quickly. Various tricks to reduce size are discussed in #299 If you need a very lightweight recorder, LiceCap uses considerably fewer resources but also has fewer features and no editor component.

kerem commented

2026-02-26 09:30:59 +03:00

Author

Owner

@GKid94 commented on GitHub (Oct 7, 2018):

@GKid94 commented on GitHub (Oct 7, 2018): ![23142](https://user-images.githubusercontent.com/18757054/46578754-b039e980-ca06-11e8-9426-429dbfd1d298.jpg) ![41231](https://user-images.githubusercontent.com/18757054/46578755-b0d28000-ca06-11e8-8ab2-5980d41b3498.jpg)

kerem commented

2026-02-26 09:30:59 +03:00

Author

Owner

@vatterspun commented on GitHub (Oct 15, 2018):

I took the time to record a very large, very long video, and you're right that RAM usage is expanding with the video generated, but I'm still only seeing 50 megs with a very large recorded video recording.

Maybe it's an issue in Win10? Screenshot of my Win7-32 program usage: https://i.imgur.com/e2eyUdw.png

@vatterspun commented on GitHub (Oct 15, 2018): I took the time to record a very large, very long video, and you're right that RAM usage is expanding with the video generated, but I'm still only seeing 50 megs with a very large recorded video recording. Maybe it's an issue in Win10? Screenshot of my Win7-32 program usage: https://i.imgur.com/e2eyUdw.png

kerem commented

2026-02-26 09:30:59 +03:00

Author

Owner

@GKid94 commented on GitHub (Oct 18, 2018):

Maybe, can you optimize the program and make it lighter on resources

@GKid94 commented on GitHub (Oct 18, 2018): Maybe, can you optimize the program and make it lighter on resources

kerem commented

2026-02-26 09:30:59 +03:00

Author

Owner

@NickeManarin commented on GitHub (Nov 13, 2019):

@GKid94 With v2.20, there's a new recorder method, it uses DirectX, so it supposed to be lighter.
Also a memory cache can be used, further improving the performance.

Now, when saving, the app needs to copy some files, so it's going to give your HDD a bit of work. So far there's no solution for that.

@NickeManarin commented on GitHub (Nov 13, 2019): @GKid94 With v2.20, there's a new recorder method, it uses DirectX, so it supposed to be lighter. Also a memory cache can be used, further improving the performance. Now, when saving, the app needs to copy some files, so it's going to give your HDD a bit of work. So far there's no solution for that.

kerem commented

2026-02-26 09:30:59 +03:00

Author

Owner

@NickeManarin commented on GitHub (Mar 3, 2020):

Closing this as there's not much else to be done.

@NickeManarin commented on GitHub (Mar 3, 2020): Closing this as there's not much else to be done.

kerem referenced this issue

2026-03-01 18:46:56 +03:00

[GH-ISSUE #299] How to generate small sizes and compression best practices #1615

kerem referenced this issue

2026-03-01 18:47:02 +03:00