The default Jira attachment limit for a video is 1 GB per file on Jira Cloud and 10 MB per file on Jira Data Center. Admins can raise either one to a ceiling of 2 GB. If your screen recording will not attach, the cause is usually one of three things: a limit set lower than the default, a missing permission, or a Cloud storage quota that is already full. Below you will find the numbers, how to check your own instance, and what to do when a video is simply too big.

Wezardapp

Capture UAT Issues Without Jira Uploads

Wezard records your screen, transcribes issues in real time, and detects duplicate tickets before they reach your Jira backlog.

Visit Wezard

TL;DR

Jira Cloud defaults to 1 GB per file. Jira Data Center and Server default to 10 MB. Both can be raised to 2 GB by an admin.
Your site’s real limit may differ from the default. An admin can read it in attachment settings, or you can query the REST API.
A video can fail even under the limit: missing Create Attachments permission, a blocked file type, odd characters in the filename, or full storage.
For large recordings, trim and compress first, or host the file elsewhere and paste a link into the issue.
Better still, record the problem in a tool that captures the video, transcript and ticket details together, so the file never has to be wrestled into Jira by hand.

Jira video attachment limits at a glance
How to find your site’s actual limit
Why a video fails to upload when it looks small enough
Shrink the video before you attach it
When the video is still too big: share a link
Practical rules for teams that attach video to Jira
Our perspective
Skip the upload struggle with Wezard
FAQ
Sources

Jira video attachment limits at a glance

Two hosting models, two very different out-of-the-box numbers. Fastio’s guide to Jira limits reports that Jira Cloud enforces 1 GB per file by default, adjustable to an absolute ceiling of 2 GB. Jira Data Center and legacy Jira Server default to 10 MB (10,485,760 bytes), reconfigurable up to 2,147,483,647 bytes, which is 2 GB.

	Jira Cloud	Jira Data Center / Server
Default per-file limit	1 GB	10 MB
Maximum per-file limit	2 GB	2 GB
Who changes it	Site admin in system settings	Admin via jira-config.properties
Extra ceiling	Plan storage quota	Your own file system or storage

Ten megabytes sounds generous for a screenshot and is tiny for video. A few seconds of full-resolution screen capture can pass it, and many teams on Data Center never change the default. FileHop’s workplace video guide notes that admins can raise it but most organizations keep the default. So if a colleague on a different Jira site says “it uploaded fine for me,” they may be on a different limit entirely.

Cloud storage is a second ceiling

On Jira Cloud, the per-file limit is not the only gate. According to ikuTeam’s attachment guide, Free plans include 2 GB of file storage per app, Standard plans 250 GB, and Premium plans are unlimited. A single 1.9 GB video could pass the file-size check and still use up a Free plan’s entire quota in one upload.

If your team stores bug recordings on tickets for months, storage adds up faster than most people expect. Plan for it the same way you plan for the per-file number.

How to find your site’s actual limit

The defaults above are starting points. Your admin may have lowered the limit, and one result Google shows for this keyword describes a site where the setting was configured far below the default. Here is how to find out what applies to you.

If you are a Jira admin

Open Jira’s system settings and look for the attachment section. There you can see whether attachments are enabled, the maximum size per file, and the attachment permissions. On Cloud, this is a site-level setting. On Data Center, the size is controlled through the jira-config.properties file, so changing it means access to the server and usually a restart window.

If you are not an admin

You can still read the number. The Jira Cloud platform REST API has an endpoint, GET /rest/api/3/attachment/meta, that returns the attachment settings, including whether attachments are enabled and the maximum allowed size in the uploadLimit field, as shown in the API request documentation. If that is more than you want to do, ask your Jira admin one question: “What is our per-file attachment limit, and is it the default?”

Testers should know this number before a UAT cycle starts. Nothing slows a test day like discovering at 3 p.m. that every recording over 10 MB is rejected.

Why a video fails to upload when it looks small enough

Size is the obvious suspect, but not the only one. According to ikuTeam’s guide, the common causes of a failed video upload are:

Missing Create Attachments permission. The guide calls it the most common silent failure. The upload seems to do nothing.
A token error. The message reads “Could not attach file, missing token,” a CSRF issue that often clears after refreshing or signing in again.
Special characters in the filename. Rename the file with letters, numbers and underscores.
A blocked file type. Your instance may block certain extensions.
Exceeding the configured limit. This typically shows as a 413 or 500 error.
A browser extension or ad blocker interfering with drag and drop.

Work through them in order of cheapness. Rename the file, try a private window with extensions off, then check permissions with your project admin. Only then start compressing.

Permission problems are especially common with outside testers and business users who were added to a project quickly. If that sounds like your UAT setup, our piece on Jira permissions for external testers covers a cleaner way to handle it.

Shrink the video before you attach it

If your limit is 10 MB, or your recording is simply bigger than the limit, reduce the file. Order matters.

1. Trim first

Cut everything before the bug appears and after it is shown. A 20-second clip that reproduces the defect is worth more to a developer than a five-minute walkthrough. Short clips are also the easiest way to stay under any limit. If you record the whole screen when only one window matters, consider capturing just that region; we explain why in partial screen recording and faster triage.

2. Lower the resolution

For screen content, 720p or 1080p is plenty, and 4K is rarely needed. FileHop’s guide suggests recording at 720p or 1080p rather than 4K for screen content and checking the result before you share it. A practical target for a tight 10 MB limit, according to Compresto’s Jira guidance, is 720p at 15 to 30 frames per second, trimmed to the relevant section. Screen recordings have little motion, so low frame rates look fine.

3. Compress, but keep the text readable

Adobe explains that you can reduce a video’s size by changing the format, trimming, lowering resolution or reducing bitrate. It also notes that lossy compression discards data to make files smaller, while lossless keeps the original data at a larger size. For bug reports, lossy is the right choice, as long as UI text, error codes and field values stay legible. Compress, then play the result and read the error message on screen. If you cannot read it, the developer will not either.

4. Plan the recording, not the rescue

FileHop recommends checking the target limit before recording and planning a shorter, lower-resolution capture, rather than trying to squeeze a 500 MB file down afterward. Post-hoc compression wastes time and often degrades quality more than a good recording setting would have.

Some recordings are legitimately long: an end-to-end UAT scenario, a performance issue that takes minutes to appear, a session with narration. For anything larger than your limit, the usual advice from several sources is the same: host the file elsewhere and put the link in the ticket.

Fastio’s guidance says files beyond the 2 GB ceiling can go to external cloud storage with a share link pasted into the description or a comment, or be split into smaller archive volumes. ikuTeam adds that hosting multi-gigabyte recordings elsewhere also keeps the instance cleaner and pages faster than a 1.9 GB video sitting in the attachments panel.

Fastio also suggests, for teams that accumulate heavy media, enforcing a rule that testers share screen recordings by external workspace link instead of attaching raw video. It also suggests auditing large issues with a JQL filter such as attachments IS NOT EMPTY AND updated < -180d and archiving attachments from closed projects.

Check the link before you paste it

A link that opens for you may not open for the developer. Before you post it in Jira:

Open it in an incognito window to see exactly what a recipient sees, as Kreatli’s sharing guide advises.
For sensitive or pre-release content, set an expiration date and a password.
Avoid “anyone with the link” for sensitive material. Kreatli points out it is convenient but easy to forward, so invited emails or workspace access are safer.

This matters in UAT because recordings often show real customer data, internal screens or unreleased features. Our article on UAT video privacy by design goes deeper on what to hide and who should see what.

Practical rules for teams that attach video to Jira

A few habits prevent most attachment trouble.

Write the limit into your test plan. State the per-file number and what to do above it.
Cap recording length. Ask testers for one defect per clip, ideally under a minute.
Name files plainly. Ticket key, short description, no special characters.
Add text next to the video. Steps, expected result and actual result in the description let a reader triage without pressing play. Our Jira bug report template gives you a starting layout.
Review storage quarterly on Cloud, so a Free or Standard quota is not silently exhausted.
Agree what counts as evidence. The rules in bug report attachments that cut triage time are a good model.

If you also work in other trackers, the same questions come up there. We cover the equivalents in Azure DevOps video attachments and ServiceNow video attachments.

Our perspective

Most teams treat the attachment limit as a Jira settings problem. We see it as a capture problem. When a tester records a long video, exports it, hunts for a compressor, then fights an upload error, the bug report has already cost more than the bug deserves.

Wezard is built around a different flow. A tester records the screen, speaks the issue, and our real-time AI transcription turns the narration into the ticket text. Our duplicate detection is designed to flag matching reports before they reach your Jira or Azure DevOps backlog, so developers get one enriched ticket instead of five near-identical ones. Because the video, transcript and details travel together into the integration, testers do not have to think about file handling.

We also believe business users should not need Jira expertise to report well. A guided submission, voice input and a simple recording are easier for a finance analyst on UAT day than a blank issue form and an attachment dialog. That is the experience we designed Wezard to deliver, with SOC 2 certification and SSO for enterprise teams.

Marketing

Skip the upload struggle with Wezard

If your UAT testers are business users, not engineers, the fewer steps between “I found a problem” and “it is in the backlog,” the better. Wezard records the screen, transcribes what the tester says as they say it, and checks for duplicates before the ticket lands in Jira, Azure DevOps or ServiceNow.

Plans are published on our pricing page: Starter is $25 per month, Team is $70 per month and Business is $160 per month. Enterprise is available with pricing on request. You can also see how teams use it on our use cases page, or read how video transcripts become bug reports.

FAQ

How big can Jira attachments be?

On Jira Cloud the default is 1 GB per file, and admins can raise it to 2 GB. On Jira Data Center the default is 10 MB, configurable up to 2 GB. Your own site may be set differently, so ask your admin or check the attachment settings.

How do I upload a video that is too large for Jira?

Trim it, lower the resolution to 720p or 1080p, and compress it, then check that text on screen is still readable. If it is still over the limit, store it in cloud storage and paste a share link into the issue description or a comment. Check the link in an incognito window first.

Why does my video fail to attach even though it is under the limit?

The usual suspects are a missing Create Attachments permission, a blocked file type, special characters in the filename, a token error, or a browser extension blocking drag and drop. On Cloud, a full storage quota can also be the cause. Try renaming the file and a private window first, then ask your project admin about permissions.

Does Jira Cloud limit total attachment storage?

Yes. According to ikuTeam, Free plans include 2 GB of file storage per app, Standard plans 250 GB, and Premium plans are unlimited. Large videos can use up a small quota quickly, so review storage as well as per-file size.

TL;DR

Table of Contents