Skip to content

Use case

Give feedback with a GIF, not a paragraph

“The hover state flickers when you scroll” is hard to write and easy to show. Record it, put an arrow on it, and paste it in the comment.

Open in the editorPreset: GitHub issues & PRs
Width
800px
Frame rate
15 fps
Target
≤ 9.2 MB
Open an empty project

How to · 3 steps

Step by step

  1. 1

    Record the moment

    Open the staging site or branch, record its tab, and do the thing that looks wrong.

  2. 2

    Point at it

    Add an Arrow or box, a numbered step per point, and slow it down if it’s fast.

  3. 3

    Paste it in the thread

    Export for GitHub, Slack, Linear or Jira; it plays inline.

Why a GIF beats a screenshot

Most UI feedback is about motion: a stutter, a jumping focus ring, a menu opening under the header. A screenshot can’t show it; a GIF plays right in the comment.

One point per GIF

Keep each GIF to 3–8 seconds and one issue, so each comment can be resolved on its own.

  • Start just before the problem so the loop makes sense.
  • Match the step number to your comment (“2: the tooltip overlaps”).
  • Slow the key moment to 0.5×, and Zoom into two-pixel details.

Size limits

Where this GIF is going

Limits for the destinations on this page. See every platform.

GIF size limits for GitHub issues & PRs, Slack, Linear, Jira
PlatformMax GIF sizeLazygif preset
GitHub issues & PRs
10 MB
800px · 15 fps · ≤ 9.2 MB
Slack
1 GB
640px · 15 fps · ≤ 9.2 MB
Linear
Not published
800px · 15 fps · ≤ 9.2 MB
Jira
1 GB
800px · 15 fps · ≤ 9.2 MB

FAQ

Questions, answered

How do I add a GIF to a GitHub pull request comment?
Export with the GitHub preset and drag the file into the comment box.
Can I slow down a glitch so people can see it?
Yes. Split around it and set that clip to 0.5×; the rest stays at normal speed.
Is my unreleased work uploaded anywhere?
No. You share only the GIF you export.

Make your first GIF now.

Record your screen or drop in a video. Free, no watermark, nothing uploaded.