Frequently Asked Questions
Everything you need to know about GIF Resizer's privacy-first, browser-based processing
- 1Is my GIF uploaded to a server?
- No. All processing happens locally in your browser using WebAssembly technology (ffmpeg.wasm). Your files never leave your device, and we don't store, track, or access your GIFs in any way. This ensures complete privacy and security for your content.
- 2What file sizes are supported?
- GIF Resizer supports files up to 50MB. This limit ensures smooth performance in most browsers. If your GIF is larger, consider compressing it first or using a smaller source file. For best results, we recommend files under 20MB.
- 3What image formats can I upload?
- Currently, only GIF files (.gif extension) are supported for the resize tool. We're working on adding support for converting other formats (MP4, WebP, PNG sequences) to GIF in future updates.
- 4How does the resize quality compare to other tools?
- We use ffmpeg's high-quality palettegen + paletteuse pipeline with Lanczos scaling. This two-stage approach generates an optimized color palette first, then applies it with advanced dithering. The result preserves color fidelity and animation smoothness better than simple resize algorithms.
- 5Can I resize animated GIFs?
- Yes! GIF Resizer is specifically designed for animated GIFs. All frames are resized proportionally, and the animation timing, loop count, and transparency are preserved. The tool maintains frame rates and does not drop frames.
- 6What dimensions can I resize to?
- You can resize to any width or height between 1 and 10,000 pixels. The tool supports custom dimensions, percentage scaling (10%-200%), and platform-specific presets for Discord, WhatsApp, and other services.
- 7Why use browser-based processing instead of server uploads?
- Browser-based processing offers several advantages: (1) Complete privacy - your files never leave your device, (2) No file size upload limits from servers, (3) Faster processing with no network transfer time, (4) Works offline once the page loads, (5) No server costs passed to users.
- 8Does it work on mobile devices?
- Yes, GIF Resizer works on modern mobile browsers that support WebAssembly, including Chrome, Safari, and Firefox on iOS and Android. However, very large files (>20MB) may have performance issues on older mobile devices due to memory limitations.
- 9Can I use this tool offline?
- Once the page and WebAssembly files are loaded, the tool works offline. Your browser caches the necessary files. However, the initial load requires an internet connection to download the ffmpeg.wasm core (~32MB).
- 10Will more tools be added?
- Yes! We're actively developing additional features: (1) GIF compression with target file size, (2) Format conversion (GIF to MP4, WebP, and vice versa), (3) GIF editing (trim, crop, speed adjustment), (4) Batch processing for multiple files, (5) GIF creation from images or videos. Check our roadmap in the sidebar for updates.
- 11Is there a watermark on processed GIFs?
- No, absolutely not. All GIFs processed through GIF Resizer are watermark-free. We believe in providing a completely free tool without any limitations or branding on your output files.
- 12Why is the tool loading ffmpeg files?
- FFmpeg is a powerful open-source multimedia framework. We use a WebAssembly-compiled version (ffmpeg.wasm) that runs in your browser. The first time you visit, your browser downloads ~32MB of ffmpeg core files. These are cached for future use, so subsequent visits load instantly.
- 13What browsers are supported?
- GIF Resizer requires a modern browser with WebAssembly support: Chrome 57+, Firefox 52+, Safari 11+, Edge 79+. Internet Explorer is not supported. For best performance, use the latest version of Chrome, Firefox, or Edge.
- 14How do I report bugs or request features?
- We welcome feedback! You can report issues or suggest features through our GitHub repository. Look for the feedback link in the site footer. We actively review all submissions and prioritize based on user needs.
- 15Is the source code open source?
- The tool is built on open-source technologies (Next.js, ffmpeg.wasm). While the site code itself is currently proprietary, we use and contribute to open-source projects. The ffmpeg.wasm library we use is fully open source and maintained by the community.