FrameShot
Guide

How to Turn a Screen Recording Into a GIF

Make small, sharp GIFs from screen recordings: when a GIF beats a video, which size and frame rate to choose, and how to keep the file light.

The FrameShot Export as GIF dialog with a trimmed part of a recording, width and frame-rate options

A short GIF is often the clearest way to show how something works: it plays by itself, loops and needs no player. It is also easy to end up with a blurry 30 MB file. Here is when a GIF is the right choice, how to make one from a screen recording in Chrome, and which settings keep it sharp and small.

When a GIF beats a video

GIFs start playing on their own and loop, almost everywhere: team chats, issue trackers, documentation, README files and many email apps (a few older desktop email apps show only the first frame). They are ideal for short, silent moments, like how a menu opens, where a button is, or what happens after a click.

Choose a video instead when you need sound or narration, when the clip is longer than about half a minute, or when the content is full of colour and motion, like a game or a film. Videos are much smaller for the same length and quality.

How to make a GIF from a recording in FrameShot

  1. Record your screen with FrameShot, or open an existing recording from the library.
  2. In the player, click Export GIF.
  3. Choose the range. Set the start and end so the GIF covers just the moment you need, up to 60 seconds.
  4. Pick a width and a frame rate: 320, 480, 640 or 800 pixels wide, at 10, 15 or 20 frames per second.
  5. Choose whether it loops forever or plays once.
  6. Export. FrameShot shows the progress and saves the GIF to your computer. Everything happens on your device, nothing is uploaded.
The Export as GIF dialog over a recording, showing the selected range, width and frame rate
Pick the part of the recording, the size and the frame rate.

Choosing size and frame rate

File size grows quickly with every setting: twice the width means about four times the pixels in every frame, and twice the frame rate means twice as many frames.

  • 640 pixels wide is a good default for docs and tickets. Use 480 for chat messages and 800 when small text must stay readable.
  • 15 fps looks smooth for most interface demos. 10 fps is enough for clicks and typing, and 20 fps helps with scrolling and animation.
  • Keep it short. Five to fifteen seconds usually tells the whole story.

Keeping GIFs small

FrameShot already does the clever part: it builds one colour palette for the whole GIF, makes pixels that don’t change from one frame to the next transparent, and merges frames that are identical. Interface recordings, where most of the screen stays still, shrink a lot that way. You can help it further:

  • Record less screen. Share a tab or a smaller window rather than a large monitor.
  • Keep the background still. Pause videos and animations you aren’t demonstrating.
  • Move the mouse calmly. Every change on screen adds data.
  • Avoid big photos and gradients. A GIF can show 256 colours per frame, so smooth gradients may look banded.

If a GIF is still too big, the clip is probably too long for a GIF. Share the video instead: FrameShot saves recordings as MP4 or WebM.

GIF or MP4?

Some websites quietly convert uploaded GIFs into videos because video is so much smaller. GitHub issues, many chat apps and most documentation tools accept short videos too. A good habit is to share a GIF for anything under fifteen seconds that should play by itself, and an MP4 for everything longer or with sound. With FrameShot you can make both from the same recording.

Try FrameShot freeFull-page screenshots and screen recording for Chrome. No watermark, no account, nothing uploaded.
Add to Chrome