Zendesk PDF Export
There is no PDF button on a Zendesk ticket and none on a help centre article. Everything else in this guide follows from that one sentence.
Why you are asking
The right route depends entirely on the reason, and there are only four common ones.
Answer that first. Teams routinely build a script for a job that a print dialog would have covered.
The one Zendesk PDF route that's genuinely built in
Reporting. Explore can deliver dashboards on a schedule, and PDF is among the delivery formats for dashboard exports on the plans that include it. Raw query results tend to come out as spreadsheet formats instead, which is usually what people wanted anyway.
So if the request is "send me the weekly numbers as a PDF every Monday", that's a scheduled delivery and you can stop reading. Check the current Zendesk docs for the export formats and scheduling options on your tier.
Tickets: print, app, or API
Print to PDF. The browser print dialog on an open ticket, saved as PDF. Free, instant, and it captures what is on screen, which may include internal notes you didn't intend to hand to a customer. Read it before you send it. For one ticket a month this is the correct answer and everything below is over-engineering.
A marketplace app. Several apps add a PDF or print action to the ticket sidebar with cleaner formatting and control over what is included. Worth it if the request is weekly rather than annual. Check what the app does with your data before installing, since a ticket transcript isn't a low-sensitivity document.
The API plus a renderer. Pull the ticket and its comments through the Ticket API, render to HTML from a template you control, then convert with a headless browser or a PDF library. This is the only route that gives you consistent branding, redaction of internal comments, and a batch of two hundred tickets at once.
Attachments are the wrinkle in all three. They're separate files with their own URLs, so a complete record means the PDF plus the attachments, not the PDF alone.
Articles: print stylesheets and the API
Same shape, different starting point. There's no export-to-PDF in Guide, and printing an article usually produces the header, the sidebar and the footer alongside the content, which looks amateurish.
The cheap fix is a print stylesheet in your theme. Twenty lines of CSS inside a print media query that hide navigation and expand any collapsed sections, and printing suddenly produces something you'd put in front of a customer. Most themes ship without one.
For a whole manual, use the Help Center API to pull articles in section order, concatenate them into one HTML document with a table of contents, and render that. The result is a real book rather than forty separate files. See exporting articles for the retrieval side.
Doing it at any scale
The moment somebody says "every ticket for this client, for the year", printing stops being an option.
The job is always the same shape. Query the tickets you need, pull each one with its comments, strip internal notes unless legal asked for them, render each to HTML from one template, then convert. A headless browser gives the best fidelity. A PDF library is faster and fussier about layout.
Three details catch people out. Pagination, because the API returns pages and a naive script quietly stops at the first hundred. Rate limits, which throttle a tight loop, so build in a delay rather than discovering it at ticket four hundred. And archived tickets, which behave differently enough that a bulk pull over old data has to be tested on old data.
Budget half a day for a working version, and another half for the formatting nobody agreed on up front.
The data request case
If somebody has asked for their personal data, don't start with PDF. Zendesk has specific facilities for user data export and deletion, and the deadline you're working to is legal rather than aesthetic.
Pull the record properly, review it, redact anything about other people, and only then decide on a format. GDPR in Zendesk and redaction cover the parts that matter. The file format is the last decision, not the first.
Frequently asked questions
Can you print a ticket or save an article as PDF?
Both, through the browser. Zendesk print ticket uses the print stylesheet, and Zendesk article to PDF is the same trick on the help centre. Neither is a supported export, which matters when somebody wants five hundred of them.
Can I export a Zendesk ticket as PDF?
Not with a native button. Print to PDF from the browser, use a marketplace app, or pull the ticket through the API and render it yourself.
Can customers download their request as a PDF?
Not by default. They can print the request page from the portal, which is why a print stylesheet in your theme is worth the twenty lines of CSS.
Can I export the whole knowledge base to PDF?
Only by building it. The Help Center API returns article bodies as HTML, and you concatenate and render them. Some marketplace apps do this for you.
Does Explore export to PDF?
Dashboard exports and scheduled deliveries include PDF among the formats on the plans that support them. Raw query data usually exports as a spreadsheet instead.
Do PDF exports include internal notes?
A browser print of the agent view includes whatever is on screen, internal comments included. Check every file before it leaves the building.
One conversation, not two files
Exporting a request is harder when it is split across two tickets. Ticket Merger merges duplicates so the record is one thread.
Start free trial14-day free trial. No credit card required.