Devlog GIFs and Short Clips That Actually Show Progress
Our last devlog post had 900 words of careful notes about a new grappling hook and one six second GIF of the hook in action. The comments were all about the GIF. Two people asked how the rope physics worked.

Our last devlog post had 900 words of careful notes about a new grappling hook and one six second GIF of the hook in action. The comments were all about the GIF. Two people asked how the rope physics worked. Nobody quoted a single sentence of the text. That pattern has repeated on every devlog we have posted for two years: the clip carries the post, and the words support it.
So this is a practical guide to devlog GIFs and short clips, the small moving pictures that show progress in a way screenshots and paragraphs cannot. It covers what to record, how long to make it, which free tools we use, and the mistakes that make a clip look worse than the game actually is.
Why Devlog GIFs Beat Screenshots for Showing Progress
A screenshot shows how your game looks. A clip shows how it feels. For a platformer, a jump arc, a landing squash and a dust puff only make sense in motion. For a puzzle game, the moment a block slides into place and the board reacts is the whole point.
Clips also make progress visible. A side by side clip of the same jump in week two and week nine tells a reader more about your work than a list of fifteen tweaks. We started doing those comparisons after reading our own older notes on how to keep a devlog people actually read, and they quickly became the most shared posts we make.
What Is Worth Recording
Not every change deserves a clip. We use a simple test: if a player would notice the change in the first minute of play, record it. If only you would notice, write a sentence instead.
Good candidates include:
- A new mechanic doing one thing well, like a dash, a grab or a combo.
- A before and after of game feel, such as adding screen shake, hit pause or particles.
- A bug that is funny or visually interesting. These get more attention than polished features, and they show honesty.
- A new level or area entered for the first time, with the camera moving.
- UI changes that only make sense when animated, like a menu transition or a health bar draining.
Things that rarely work as clips: refactored code, balance number changes, and anything that needs a paragraph of setup before the viewer understands what they are looking at.
The Ideal Length Is Shorter Than You Think
Our best clips run between three and eight seconds. Longer clips lose viewers before the interesting moment arrives, and on most social platforms autoplay loops make short clips repeat, which is exactly what you want. A six second loop seen three times beats an eighteen second clip seen once.
Start the clip a half second before the action and end it a half second after. If the loop point can be seamless, with the character returning to the starting pose, even better. Viewers watch a clean loop far longer than they intend to.
Free Tools That Do the Job
You do not need paid capture software. These are the tools we actually use on a mixed Windows and Mac team.
| Tool | What we use it for | Cost |
|---|---|---|
| OBS Studio | Recording gameplay at a fixed frame rate and region | Free |
| ShareX (Windows) | Quick region capture straight to GIF or MP4 | Free |
| Kap (Mac) | Short screen captures with simple trimming | Free |
| ScreenToGif (Windows) | Frame by frame trimming and loop editing | Free |
| ffmpeg | Converting and shrinking files in batch | Free |
For Scratch projects, record the stage in full screen mode so the editor panels do not appear at the edges. Set the capture region to exactly the game area, not your whole monitor.
Why You Should Often Skip the Actual GIF Format
The usual advice says to post GIFs because they autoplay everywhere. That was true ten years ago. Today, GIF is often the worst way to share a game clip.
GIFs are limited to 256 colors per frame, so gradients band and pixel art palettes sometimes shift. They are also huge. A ten second GIF at 60 frames per second can easily pass 15 MB, while the same clip as an MP4 sits under 1 MB and looks sharper. Most platforms, including Discord, Mastodon and most devlog hosts, autoplay short muted MP4 or WebM files just like GIFs.
We now record everything as MP4 and only export a GIF when a platform truly requires it. When we do, we drop to 30 frames per second and trim the width to 640 pixels, which keeps most clips under 5 MB.
Recording Mistakes That Make Your Game Look Worse
A visible mouse cursor
Hide it in your capture settings or move it off the game area. A stray arrow in the corner makes a clip feel like a bug report.
Recording at a low frame rate
If your game runs at 60 frames per second and you capture at 15, smooth motion turns choppy and viewers blame the game. Capture at the game's native rate, then reduce later if needed.
Showing debug overlays
Collision boxes and frame counters are fascinating to developers and confusing to everyone else. Turn them off unless the clip is specifically about them.
Playing badly on camera
Record five takes and keep the cleanest one. A clip of you missing the jump three times does not show off the jump.
Building a Clip Habit Into Your Week
The hardest part is remembering to record before the feature changes again. We keep a single shared folder named by week number. Whenever someone finishes something visible, they drop a raw capture in before moving on. On devlog day, we pick the two or three best clips instead of scrambling to stage new ones.
That folder also became our record of what we cut. When we wrote about cutting features from our game, the clips of abandoned mechanics made the post far more honest than a list could.
FAQ
Should devlog clips have sound?
Most clips autoplay muted, so design them to make sense without audio. If sound is the point, such as a new music system, post a separate clip and say so in the caption.
How many clips should one devlog post include?
Two to four is a good range. One clip per major change, placed right next to the paragraph that explains it, keeps the post readable without turning it into a gallery.
Is it worth adding captions or text overlays?
A short label such as "week 2" and "week 9" on comparison clips helps a lot. Long text overlays usually do not, because viewers will not pause the loop to read them.
Start With One Clip This Week
Pick the most visible change you made in the last seven days, record five takes as MP4, trim the best one to six seconds, and put it at the top of your next post. For more on writing up your progress, see our devlog archive.
More in Devlogs
Devlogs
Adding Sound and Music to Our Godot Game, a Devlog
We shipped the platformer demo to eleven playtesters with no audio at all, because audio was the thing we kept pushing to next...
Devlogs
Adding Godot Screen Shake and Hit Stop, a Devlog
The most upvoted comment in our last feedback thread was four words long: "hits feel like nothing." Eleven other players agreed...
Devlogs
Adding Controller Support to Our Godot Game, a Devlog
Three of the first ten people who played our demo picked up a gamepad, pressed A on the title screen, and nothing happened.