How do I export Jira issues to PDF for free?

Filter your issues to the set you need, reduce the visible columns to the essentials, then use your browser's print function and choose 'Save as PDF' as the destination. Set orientation to landscape and disable browser headers and footers for a cleaner result. This requires no app and no additional cost.

Does Jira have a built-in PDF export?

Jira offers printable views for individual issues and export options such as CSV and XML for issue lists, but there is no dedicated formatted PDF export for a list of issues. Producing a PDF natively means printing a view to PDF through your browser.

When is a PDF export app worth paying for?

When you produce formatted reports regularly and need consistent templates, your own branding, control over layout and page breaks, or scheduled automatic generation and delivery. For an occasional one-off export, the browser print method is usually adequate and free.

How to export Jira issues to PDF for free, without an app

There's no "Export to PDF" button for a list of Jira issues. There's CSV, there's XML, there's a printable view for a single issue — but no formatted PDF export for a filtered list. So people either buy an app or assume it can't be done.

It can be done, for free, and for occasional use it's perfectly adequate. Here's the method, and more importantly, the settings that decide whether the result is readable or a mess.

The native method

Filter first. Open your issue search or board and narrow the results to exactly what belongs in the document — a project, a time window, a status. A PDF of 200 issues is unreadable whatever you do to it.
Cut the columns. This is the step that matters most and the one everyone skips. In the issue view's column settings, reduce to the fields a reader genuinely needs — typically summary and status, maybe assignee and due date. Every column you remove gives the rest room to be legible.
Print the page. Ctrl/Cmd + P opens your browser's print dialog.
Choose "Save as PDF" as the destination.
Set orientation to landscape. Issue tables are wide; portrait pages are not. This single setting rescues most exports.
Turn off headers and footers in the print dialog's options, so you don't get the URL and a timestamp stamped across your document.
Adjust the scale if content still overflows — most browsers offer a scale percentage or a "fit to page width" option.

Save it, open it, and check the page breaks before you send it anywhere.

Exporting a single issue

For one issue rather than a list, Jira's own printable/export view for an issue gives you a cleaner starting point than printing the normal screen — it strips the interface chrome and lays the fields out for reading. Print that to PDF using the same browser steps above.

Why the output looks the way it does

Worth understanding, because it tells you what you can and can't fix.

You aren't generating a document. You're printing a web page. Jira's interface is designed to be variable-width, scrollable and interactive; a PDF page is a fixed rectangle with mandatory page breaks. The browser does its best to force one into the other, which is why wide tables overflow, page breaks land mid-row, and anything collapsible renders oddly.

That's also why reducing columns helps more than any other adjustment: you're reducing the width the browser has to cram onto the page, which is the root of the problem.

The free alternative worth considering: CSV

If the recipient is going to work with the data rather than read it as a document, export to CSV instead and let them open it in a spreadsheet. It's a native Jira export, the formatting problem disappears entirely, and they can sort and filter for themselves. A PDF is the right format for "read this"; a spreadsheet is the right format for "use this."

When to pay for an app

The Marketplace has apps built specifically for PDF export, and they solve real problems the browser method can't:

Templates, so every report looks the same without you fiddling with print settings.
Branding — your logo, your colours, a cover page.
Layout control, including deliberate page breaks and grouped sections.
Scheduled generation and delivery, so the report produces and sends itself.

If you generate formatted reports weekly and the output goes to clients or executives, that's a genuine recurring cost you're paying in fiddling, and an app pays for itself. If you export twice a year, it doesn't.

One thing worth asking before you automate the PDF

If you're setting up a recurring PDF because someone needs to stay informed, notice that you're automating the production of a document that is out of date the moment it's generated, and that the recipient can't check between sends.

Sometimes that's genuinely the requirement — a formal record, a contractual deliverable, something that must be frozen and archived. Then a good PDF is exactly right, and it's worth setting up properly.

But if the underlying need is "keep this person in the loop," a scheduled email summary or something they can open and check themselves solves that better than any PDF, however well formatted. The weekly Jira PDF export trap is the longer argument for why. Fix the export if you need the export; just check that you do.

I'm Andrey. I build small, focused apps for Jira at Guenov Labs, and I write about the unglamorous parts of reporting on technical work.