Skip to content

Use case

Bug report GIFs that make the repro obvious

“It doesn’t work” becomes a five-second loop of exactly what happened. Record it, blur what shouldn’t be shared, and paste it in the ticket.

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 repro

    Start just before the steps that trigger it and stop just after.

  2. 2

    Redact and mark it

    Blur tokens and customer data, box the broken element, and slow the moment down.

  3. 3

    Export and attach

    The GitHub preset fits 10 MB, which also suits Jira, Linear and Slack.

Show the steps, not just the error

Include the two or three actions before the failure; that’s what makes it reproducible. Keep it under about 15 seconds, and add a caption like “clicks Save → spinner never stops” so the start is clear on loop.

Catch fast glitches

Split around a flicker or layout jump, slow it to 0.5× and box the element. Export at 15 fps or more so it isn’t lost between frames. For long repros an engineer will scrub through, export MP4.

Size limits

Where this GIF is going

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

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

FAQ

Questions, answered

What’s the attachment limit for GIFs on GitHub issues?
10 MB. The GitHub preset fits under it.
Is it safe to record internal tools with Lazygif?
Yes. Nothing is uploaded; blur anything sensitive before you attach the GIF, since the ticket is where it gets shared.
Do Jira and Linear accept GIFs?
Yes, both show them inline. Under 10 MB keeps tickets quick to open.

Make your first GIF now.

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