TrackersHow-toDeveloper Workflow

Screen recording for Notion, Linear, and Jira tickets in 2026: the per-tracker workflows

Each tracker handles video attachments differently — preview behavior, file-size caps, format support, embed quirks. Here's the actual 2026 workflow for shipping screen recordings into Notion, Linear, and Jira tickets without bouncing off platform limits.

M. H. TawfikPublished May 26, 202614 min read

Notion, Linear, and Jira each have different opinions about what a video attachment should be. Notion expects an embed; Linear treats it as a first-class inline asset; Jira treats it like a 2012 file attachment with a generous-but-not-truly-generous size cap. Knowing the differences saves you the loop of "exported, attached, attachment failed, exported smaller, attached again, finally worked". This post is the actual 2026 per-tracker workflow — what file size, what format, what the inline-preview behavior is, and how to ship a recording into each of the three without thinking about it.

TL;DR — the per-tracker matrix

Tracker	Max attachment	Format that previews inline	Ideal target size	Quality tier
Notion (free)	5 MB	MP4 (H.264)	Under 5 MB	Low (720p)
Notion (paid)	5 GB	MP4 (H.264)	Under 50 MB	Medium (1080p)
Linear	100 MB	MP4 + WebM	Under 25 MB	Medium (1080p)
Jira Cloud	10 MB default	MP4 only	Under 5 MB	Low (720p)
Jira Data Center	Configurable (often 50 MB)	MP4 + WebM	Under 25 MB	Medium (1080p)

The single most useful number: Jira Cloud's default 10 MB cap is the most common QA workflow blocker — a 60-second recording at 1080p Medium is 37 MB, far over the limit. Everything below the matrix is making this work without trimming compromise.

Notion: the most format-restrictive of the three

Notion treats video attachments as either uploads (live in the page, count against workspace storage) or embeds (link to YouTube/Loom/Vimeo, no storage cost). Per workspace plan:

Free plan: 5 MB max per upload. This is genuinely tiny — barely enough for a 10-second 720p clip.

Paid plans (Plus, Business, Enterprise): 5 GB per upload. Generous; you'll never bump into it for a normal-length recording.

The Notion-specific workflow

For a free-tier Notion page:

Record in ClearRec at Low tier (720p / 30 fps / 2.5 Mbps).
Keep the recording under 15 seconds — that's ~5 MB at Low tier.
Export MP4.
Drag the file into the Notion page (or use /video to insert).
The video previews inline with a play button.

If the recording must be longer than ~15 seconds, the 5 MB cap forces a different path: upload to YouTube (unlisted), then embed the YouTube URL in Notion via /video. The recording lives on YouTube; the Notion page just shows a YouTube embed.

For paid Notion workspaces:

Record at Medium tier (1080p / 30 fps / 5 Mbps).
Recordings up to about 10 minutes will fit comfortably (~370 MB at the upper end, still under the 5 GB cap).
Drag into Notion. Inline preview works.

Format and codec specifics for Notion

MP4 (H.264 + AAC) is the safest format. Notion's previewer is built around HTML5 <video> with broad codec support, but H.264 inside MP4 is the only combination we've never seen fail.
WebM (VP9) sometimes fails preview on older Notion clients, particularly the desktop apps that haven't been updated in a while. The web app handles WebM fine in 2026, but the desktop apps occasionally fall back to "click to download" instead of inline preview.
GIF is the wrong choice. For the same recording, GIF is ~15× the size of MP4. Notion respects animated GIFs, but you'll hit the 5 MB free-tier cap on essentially any GIF that isn't 3 seconds long. (Full reasoning in MP4 vs WebM vs GIF.)

Notion gotchas

Auto-play is off by default. Notion's inline video preview requires a click to start playing. This is generally good for long pages with multiple videos.
Mobile rendering is inconsistent. Notion's iOS and Android apps sometimes show videos as a "tap to view" placeholder instead of an inline preview. Test on mobile if your audience uses Notion mobile.
Embedded video in tables/databases works but is slow. If you're embedding videos in a Notion database (e.g., a bug tracker page where each row has a recording), the database performance degrades noticeably above ~20 videos. Use links to externally-hosted videos instead.
Video files don't sync to "Available offline" in the Notion desktop app. The page metadata syncs offline; video files do not. Plan accordingly.

Linear: the most QA-friendly tracker in 2026

Linear's video attachment story is the best of the three. The 100 MB per-attachment cap is enough for almost any single-bug recording, the inline previewer is fast, and the drag-and-drop UX is the smoothest.

The Linear-specific workflow

The standard path:

Record in ClearRec at Medium tier (1080p / 30 fps / 5 Mbps).
Trim to the relevant portion (Linear's previewer is fast but reviewer attention is finite).
Export MP4.
Drag the file into the Linear issue's description or comment field.
Linear uploads the file and renders an inline <video> preview with controls.

For most bug reports, a 30-second 1080p Medium recording (~18 MB) is well within the cap and previews instantly.

Format and codec specifics for Linear

MP4 (H.264 + AAC) is the primary recommendation. Inline preview is reliable on every Linear client (web, desktop, mobile).
WebM (VP9) works in the web client and recent desktop builds. If you have a known-modern audience, WebM saves ~30% on file size at the same quality.
GIF works for short loops (under 5 MB) but Linear's inline GIF rendering is <img>-based, which means the playback can't be paused. Use MP4 for anything you want the viewer to be able to scrub.

Linear gotchas

The previewer caps at ~10 minutes. For longer recordings, Linear shows a download link instead of an inline preview. This is fine for documentation captures; less great for bug-report-style "watch this 12-minute repro".
Uploads are tied to the workspace's storage quota. Linear's pricing scales storage with seat count; you're unlikely to hit it with normal recording use, but theoretical limits exist.
The video URL is stable. Once Linear assigns a URL to an uploaded video, you can link to it from other Linear issues. Useful for "I filed a separate ticket for the same bug here — see the same video".

Jira: the most file-size-restrictive of the three

Jira Cloud's default 10 MB cap per attachment is the single most common QA pain point in 2026. A 60-second 1080p Medium recording is 37 MB. The cap can be raised by a Jira admin (it's a setting under Jira Settings → Issues → Issue attachments) but most teams don't, and the default is what you'll hit.

Jira Data Center installations are usually configured higher — often 50 MB, sometimes 100 MB.

The Jira-specific workflow

For Jira Cloud with the default cap:

Record in ClearRec at Low tier (720p / 30 fps / 2.5 Mbps).
Trim aggressively to under 30 seconds.
Export MP4.
The resulting file is ~9 MB, comfortably under the 10 MB cap.
Drag the file into the Jira issue's attachments section (or use the paperclip icon).
The file uploads and appears in the attachments list.

The inline preview behavior depends on the Jira version:

Jira Cloud (current 2026): inline preview for MP4 with a click-to-play overlay. Reasonably fast.
Jira Data Center 9.x+: inline preview supported.
Jira Data Center 8.x and older: usually shows a download link, no inline preview. Hopefully your team is on something newer.

If you need to ship a recording over the 10 MB cap on Jira Cloud and your admin won't raise it, two paths:

Path A: Re-encode with stronger compression. ClearRec's compression workflow — drop resolution to 720p, drop frame rate to 30 fps, drop bitrate to 2.5 Mbps. Most 60-second recordings will fit under 10 MB this way.

Path B: Upload to a separate host (Drive, Loom, YouTube unlisted) and paste a link in the ticket description. The recording isn't an attachment; it's a link. Works fine, but introduces an external dependency.

Format and codec specifics for Jira

MP4 (H.264 + AAC) is the only safe format. Jira's inline preview is finicky about codecs; we've seen WebM fail to preview on multiple Jira Cloud workspaces.
AVI, MOV, MKV will upload but won't preview inline. They appear as download links only.
GIF works for very short loops but the 10 MB cap kills it for anything beyond ~3 seconds.

Jira gotchas

The default 10 MB cap is per-attachment, but Jira also has a per-issue cap on total attachments (~250 MB default). For tickets with multiple recordings, watch the total.
Some Jira workflows strip attachments when transitioning between statuses. Confirm with your admin before assuming attachments persist across ticket lifecycle.
Jira's mobile apps preview MP4 inline but rendering varies by Android/iOS version. Test if you have mobile-heavy reviewers.
The default file naming convention in Jira's URL is opaque (attachment/123456/recording.mp4). When sharing a direct link, the URL doesn't tell the reviewer what's in the file. Compensate with a clear filename in your original upload.

Cross-tracker conventions that scale

A few patterns that work regardless of which tracker your team uses:

1. Naming files for clarity

The naming convention from the QA workflow post applies here:

<area>-<symptom>-<build>.mp4

auth-login-redirect-loop-rc-12.5.mp4 is parseable; screen-recording-2026-05-26-14-32-04.mp4 isn't. The convention is more important in Jira than in Notion or Linear because Jira's UI surfaces the raw filename in attachment lists.

2. Always paste the console error text next to the video

Videos are for context; text is for grep. A bug report with both — a 12-second video showing the failure plus a code block with the stack trace — is dramatically more findable in tracker search than a video-only report.

3. One video per ticket

Don't bundle five recordings into one ticket. If you have five bugs, file five tickets. Tracker UIs are built around one-issue-per-issue, and reviewers triage faster when they can see the bug, the video, and the fix in a tight scope.

4. Avoid hosting videos in chat-only channels

A recording dropped into Slack is fine for "look at this", but Slack messages disappear from search after a while in busy workspaces. If the bug needs to be triaged or fixed, the recording belongs in the tracker, not in the chat thread that links to the tracker. The chat thread can link to the tracker, but the tracker is the source of truth.

5. Keep a local copy of every recording

Trackers occasionally lose attachments (storage migrations, retention policies, admin mistakes). For any bug you care about, keep the original MP4 on your laptop or in a personal Drive folder. The 10-minute-after-the-fact retrieval pattern is annoying when a recording is unrecoverable.

When to push for higher attachment caps

If your team uses Jira Cloud and routinely bumps into the 10 MB cap, push your admin to raise it. The justification is straightforward:

A 60-second 1080p MP4 is the right size for most bug reports, and it's roughly 37 MB. The current cap forces you to either trim too aggressively, drop resolution too far, or host externally — none of which serve the workflow.
Atlassian's own documentation supports raising the cap to 50 MB or 100 MB. The default exists for legacy reasons, not for technical ones.
The storage cost is essentially zero at modern object-storage prices. Even at scale, 100 MB × 10,000 attachments is 1 TB, which is ~$20-25 per month on any modern cloud.

The conversation with the admin is one sentence: "Can we raise the per-attachment cap from 10 MB to 50 MB? Bug-report videos at usable quality are bouncing off the current limit, which is creating workflow friction for QA and engineering." Most admins approve this in under five minutes.

Frequently asked questions

Q: What format should I use for Notion video attachments? MP4 (H.264 + AAC). This is the format with the most reliable inline-preview behavior across Notion's web app, desktop apps, and mobile apps. WebM works on the web but sometimes fails on desktop.

Q: What's Linear's video attachment limit? 100 MB per attachment. This is the most generous of the three major trackers and accommodates most single-bug recordings without trimming compromise.

Q: What's Jira's default video attachment size limit? 10 MB per attachment in Jira Cloud. This is the most common workflow blocker. Admins can raise it; ask yours.

Q: How do I attach a screen recording to a Jira ticket? Drag the MP4 onto the issue body or comment field, or click the paperclip icon and select the file. Jira uploads it; the attachment appears in the issue's attachments list with an inline preview (in modern Jira versions).

Q: How do I embed a video in a Notion page? Two options: (1) drag the file into the page (or use /video and upload) — limited by the 5 MB free-tier cap; (2) use /video and paste a URL to YouTube, Loom, or Vimeo for free hosting.

Q: Can I record a screen recording directly inside Linear? No — Linear doesn't have a built-in recorder. Use a Chrome screen recorder like ClearRec to capture the recording, then drag it into the Linear issue.

Q: Why does my video attachment fail to upload to Jira? Most likely the file exceeds the 10 MB cap (default in Jira Cloud). Re-encode with stronger compression, or upload to an external host and link.

Q: Should I use WebM or MP4 for tracker attachments? MP4 for cross-tracker safety. WebM is smaller at the same quality but inline preview is less reliable across all three trackers. The bandwidth savings rarely justify the support-burden risk.

Q: How do I keep videos searchable in my tracker? Trackers don't search video content. Always pair the video with text in the ticket body — the console error, the steps to reproduce, the expected vs actual behavior — and rely on the text for search. (Trackers' built-in text search will find tickets via the body text; the video is the proof, not the index.)

Q: Do trackers have a video preview thumbnail?

Notion: yes, shows the first frame as a preview thumbnail.
Linear: yes, shows a thumbnail with a play overlay.
Jira Cloud: shows an MP4-icon thumbnail by default in some versions; some show first-frame thumbnails. Inconsistent.

Q: What's the longest video I should attach to a ticket? For a bug report: 7-15 seconds is ideal, 30 seconds is the upper bound. For a feature walk-through or design discussion: 2-5 minutes is reasonable. Anything beyond 5 minutes usually belongs in a docs page, not a ticket.

Q: Can I attach a video to a Linear comment, not just the issue body? Yes. Linear treats attachments in comments as first-class — they upload, preview inline, and persist for the life of the comment.

The summary

The three trackers are calibrated differently:

Notion: format-restrictive (free tier caps at 5 MB, MP4 only for reliable inline preview).
Linear: most generous (100 MB cap, drag-and-drop, inline preview reliable).
Jira: most file-size-restrictive (10 MB default cap, MP4 only).

For workflow scale across all three, the safe default is: MP4 H.264, ClearRec Medium tier (1080p / 30 fps / 5 Mbps), trim to under 30 seconds, target under 10 MB. That setting clears every cap on the matrix above.

Install ClearRec from the Chrome Web Store. Record at Medium, trim, MP4 in your Downloads folder, drag into the ticket. The whole loop from "I see the bug" to "ticket has a video" is under two minutes per ticket once the workflow is automatic.