Use case
Changelog and release-note GIFs, one per change
A five-second loop next to each entry says more than the paragraph above it. Keep the set consistent and the page light.
Open in the editorPreset: GitHub issues & PRs
- Width
- 800px
- Frame rate
- 15 fps
- Target
- ≤ 9.2 MB
How to · 3 steps
Step by step
- 1
Record the release in one take
Walk through every change; Tidy up trims and speeds up the gaps.
- 2
Split it per entry
Press S between changes and delete the gaps, keeping the same zoom and style.
- 3
Export the set
Export each clip separately saves one GIF per change in one pass.
Budget the page, not just the file
Eight 5 MB GIFs make a 40 MB page. Give each GIF 2–4 MB at 800 px and 12–15 fps: enough for a 5–8 second UI clip, and under GitHub’s 10 MB and Notion’s free 5 MB.
Make the set look designed
Readers scan a changelog, so matching frames help them compare.
- One width (800 px) and one canvas shape for every entry.
- The same Background and caption position.
- Hold the final state for a second before the loop restarts.
- Skip GIFs for fixes and API changes; a sentence is faster.
| Platform | Max GIF size | Lazygif preset |
|---|---|---|
GitHub issues & PRs | 10 MB | 800px · 15 fps · ≤ 9.2 MB |
Notion | 5 MB | 800px · 15 fps · ≤ 4.6 MB |
Intercom articles | 104 MB | 650px · 15 fps · ≤ 4.6 MB |
Email (Gmail, Outlook, Apple Mail) | No fixed limit | 600px · 10 fps · ≤ 922 KB |
FAQ
Questions, answered
How big should a changelog GIF be?
2–4 MB at about 800 px wide, so a page with several entries still loads fast.
Can I make several GIFs from one recording?
Yes. Split it with S, then use Export each clip separately.
Will the GIFs work in our release email?
Mostly. Desktop Outlook on Windows shows only the first frame, so set it to the finished change. See email GIFs.
Related
Keep going
- Feature announcementsA good launch GIF shows one thing changing, readable without sound or a click. Record it, frame it, and export it sized for where you’re posting.
X · 15 MB - Email GIFsVideo doesn’t play in email; GIFs mostly do. The exceptions are predictable, so design around them.
Email · ≤ 0.9 MB - GitHub README & PRsA demo GIF at the top of a README answers “what does this do?” before anyone reads. In a PR, it saves the reviewer a checkout.
GitHub README · 25 MB - Docs & tutorialsA short loop next to each step shows exactly where to click, right where people are reading.
Notion · 5 MB
Make your first GIF now.
Record your screen or drop in a video. Free, no watermark, nothing uploaded.