for jira

Drop a cap on that Jira GIF.

Jira's default attachment cap is 10 mb. Raw screen recordings overshoot in seconds. Compress wrong and the bug isn't readable.

gifcap encoding a bug-repro gif for a jira ticket — bug repro · under 10 mb · readable

jira default attachment cap is 10 mb · raw recordings overshoot · compressed too hard, the bug isn't visible · ticket-attachment workflow shouldn't take three apps

gifcap. record your bug repro with obs/sharex/built-in recorder. drop the clip in gifcap. set the cap to 8 mb (under jira's 10). attach to the ticket. one workflow.

axis	manual ffmpeg / online tools	gifcap
hits jira's 10 mb cap on first try	trial-and-error	always — binary search
bug-repro readability	compromised by aggressive compression	gifski preserves detail
workflow	record, upload, compress, redownload, attach	record, drop, attach
privacy	repro leaves your machine	stays local
cost	free	free tier; pro $29 lifetime

runs offline. no upload bar. same gifski engine as gifski.app. free tier covers 90% of use cases.

How gifcap solves this — in detail

Jira tickets live or die on bug-repro clarity. A 30-second screen recording that doesn't survive Jira's 10 MB attachment cap is worse than no recording — it forces the engineer to ask "can you reproduce" again, restarting the loop. The gap between recording and a Jira-ready GIF is exactly where most engineering teams lose time.

gifcap collapses that gap. Drop the OBS or ShareX or Snipping Tool recording in, set the cap to 8 MB (with 2 MB safety margin under Jira's default), gifcap binary-searches quality until it fits. The bug stays visible because gifski's per-frame palette preserves UI text and color contrast at the resolution that matters for the repro.

For privacy-sensitive bugs (production data, internal tooling, customer screens), the local-encode pattern matters: the recording never leaves your machine. Online compressors require uploading the source — fine for a marketing GIF, not fine for a customer-data screenshot.

Jira — attachment limits

Default attachment size cap: 10 MB per file
Configurable max (Jira admin): up to 20 MB
Jira Cloud vs. Server: defaults differ slightly; check with your admin
Inline GIF in comments: drag-drop into the editor; autoplays in the issue view
Multi-file attachment: no per-issue cap on count, but storage quota applies per project
Acceptable formats for inline render: GIF, PNG, JPG; MP4 attaches but doesn't autoplay

download free see pricing — $29 lifetime 18 mb installer · signed · windows 10/11

FAQ

what's the max attachment size in jira?

10 mb per file by default, configurable up to 20 mb by jira admins. cloud and server defaults differ slightly; check with your admin if you need larger.

why does my bug-repro gif look blurry in the ticket?

two common causes: (1) downscaled too aggressively to fit the cap, (2) encoder used a single global palette. gifcap's binary-search holds quality as high as possible while fitting; gifski uses per-frame palettes for sharper detail.

can jira embed gifs inline in comments?

yes — drag a gif into the comment editor and it embeds inline with autoplay. same 10 mb cap applies.

how should i frame a bug repro gif?

start one second before the bug, capture two seconds of the bug, end one second after. trim aggressively. clear, narrow framing reads better at low file sizes than a full-window recording.

last updated 2026-04-22 by alain · alain@gamutcreative.tv