How to Make a GIF from a Video (Free, No Watermark)

GIFs autoplay everywhere. Unlike video files, which often require a click to play, GIFs loop automatically in emails, chat apps, forums, GitHub issues, Notion pages, and social media feeds. They don't have audio, which makes them less intrusive in work contexts.

GIFs are also universally supported. Every browser, email client, and messaging app from the last 30 years can display a GIF. Try embedding an MP4 in a GitHub comment or a Jira ticket — it won't work. A GIF just works.

The trade-off is file size. GIFs use a simple compression algorithm from 1987 and are limited to 256 colors per frame, which makes them significantly larger than modern video formats for the same content. Keeping GIFs short (under 10 seconds) and appropriately sized is key to keeping them practical.

ClipUtils Video to GIF converter processes everything in your browser — no server upload, no account.

1. Open ClipUtils Video to GIF at cliputils.com/tools/video-to-gif 2. Drop your video file (MP4, MOV, WebM, or any common format) 3. Select the portion of the video you want to convert — drag the start and end handles on the timeline 4. Choose your output settings: resolution (width), frame rate, and quality 5. Click 'Convert to GIF' 6. Preview the result and download

The converter shows you a live preview so you can adjust settings before committing to the full conversion. Processing happens locally using WebAssembly, so large files won't fail due to upload limits.

The right settings depend on where you're using the GIF:

Slack / Discord / chat: 480px wide, 10-15 fps, 3-5 seconds max. Chat apps often have upload limits (Slack: 1 MB for free workspaces) and small display sizes. A 480px-wide GIF at 10 fps looks smooth enough for a reaction GIF while staying under 1 MB.

GitHub / documentation: 720px wide, 15 fps, up to 10 seconds. GitHub renders GIFs in comments and READMEs. A higher resolution helps when showing UI interactions or code. GitHub's file size limit for inline images is 10 MB.

Email: 600px wide, 10 fps, under 3 seconds. Many email clients won't load GIFs over 1 MB, and some (like older Outlook) show only the first frame. Keep email GIFs small and make the first frame meaningful.

Social media: Consider using video instead. Twitter, Reddit, and Facebook all support native video which will look better and load faster than a large GIF. Use GIFs for social media only when the platform specifically expects them.

GIF file size grows quickly. A 5-second clip at 720p and 30fps can easily hit 20 MB. Here's how to shrink it:

Reduce resolution: Halving the width reduces file size by roughly 75% (because both dimensions decrease). Most GIFs look fine at 480px or even 320px wide.

Lower the frame rate: 30fps is overkill for GIFs. 10-15 fps looks smooth enough for most content and cuts the frame count (and file size) in half or more.

Shorter duration: Every additional second adds more frames. Trim to the essential moment. The best GIFs are 2-5 seconds long.

Simpler content: GIFs compress well when large areas of the frame stay the same between frames. Screen recordings with a static background compress much better than handheld camera footage with constant motion.

Use fewer colors: GIF supports up to 256 colors per frame. If your GIF is a screen recording or animation with a limited palette, reducing the color count can save significant space.