Image hosting for Jira repros that survive attachment sprawl.
Jira's native attachments are fine, but they duplicate across every ticket, eat tenant storage, and break when tickets get archived. External CDN URLs keep your repros accessible forever.
Upload an image →Why hosting matters on Jira
Survive ticket archival
When your org archives old Jira projects, attached images are often deleted. External URLs on ImageToURL remain.
One image, many tickets
A UI mockup or architecture diagram referenced from 10+ related tickets and the umbrella epic. Upload once, reference everywhere.
Confluence + Jira consistency
Same image in a Confluence page AND the tracking Jira ticket. External URL = one source of truth, no re-upload.
Share with non-Jira users
Stakeholders, customers, auditors who don't have Jira access can't fetch attachments. Public CDN URLs work for anyone with a browser.
How to embed
Take screenshot + upload
Snip the repro, drop the file here, copy the URL.
Paste into the ticket body
Use Jira's markdown: . Alternatively Atlassian Document Format's image node accepts the URL in the source attribute.
Link from Confluence too
Same URL in the related Confluence page's /image macro. Changes in one don't require re-upload.
FAQ
Does Jira's markdown support inline external images?
Yes —  renders inline in ticket descriptions, comments, and wiki pages. Same syntax works in Confluence.
What about attachments vs inline?
Attachments live in Jira's storage and get rehosted to an internal URL. Inline external URLs render from our CDN. Attachments are better for legal-discoverable artifacts; external is better for repros and references.
Can I drag an ImageToURL URL into the Jira editor?
Some Jira versions attempt to download and re-attach. To keep external-only, paste the markdown  directly in source mode.
Is this compliant with our SOC 2 / ISO evidence?
If your security team requires all attachments in tenant-controlled storage, native Jira attachments are the safer path. For non-sensitive screenshots, external hosting is usually acceptable.
Does this work with Jira Cloud and Server?
Both. Cloud and Data Center both accept external image URLs in markdown. Behavior is identical.
What about Jira Product Discovery?
Product Discovery's idea descriptions use the same editor — external URLs render inline.
API upload from a bug-report tool?
Yes — POST to /api/upload with a Pro/Business API key. Integrate into Sentry, Bugsnag, or custom QA tooling to auto-host repro screenshots.
Permissions?
ImageToURL URLs are publicly reachable (URL-based access). Don't use for confidential repros — use Jira native attachments for those.