Where does GIF Speed and FPS Changer process the file?
With GIF Speed and FPS Changer, the default path reads the selected file in this browser. It is uploaded only if you explicitly choose the secure worker fallback.
GIF & Video · Browser-first processing
Speed up or slow down an animated GIF while preserving looping. The default path runs in this browser. If this browser cannot decode the media or the file exceeds the local limit, you can explicitly choose the secure worker fallback.
Select a supported file or enter the requested values, then run the tool.
This browser path does not upload the selected source to ImgNimble. Closing or refreshing clears the selected files and generated result from the page.
Use this only when the browser cannot decode/encode the file or the local operation is too large. Choosing this fallback uploads the selected file to the configured secure worker and consumes 1 anonymous/member credit(s).
Common questions
With GIF Speed and FPS Changer, the default path reads the selected file in this browser. It is uploaded only if you explicitly choose the secure worker fallback.
The GIF Speed and FPS Changer worker result is temporary and is deleted by the retention cleanup schedule, normally within 24 hours.
For GIF Speed and FPS Changer, animation and video processing is CPU intensive. Local caps protect mobile stability; larger or unsupported files can use the consent-based worker fallback.
GIF Speed and FPS Changer validates the selected file before processing. Use GIF within the 35 MB per-file limit. Keep an untouched original for comparison.
For GIF Speed and FPS Changer, the local path creates the output in browser memory. If you choose worker fallback, the upload uses HTTPS and the result is returned through an expiring signed download.
Practical checks
Keep the original, inspect the generated output and confirm the current destination requirements before replacing or submitting a file.