How to Generate PDFs From Salesforce: The Complete Guide (2026)

Salesforce does not have a built-in PDF generator as a core platform feature. Visualforce pages can be rendered as PDFs and some Salesforce features generate basic PDF outputs, but these are not usable as a general document generation solution for business documents like contracts, invoices, and proposals.

To generate PDFs from Salesforce at the quality and flexibility required for business use, you need a dedicated document generation app installed in your org. These apps are available on the Salesforce AppExchange and range from integration-based tools that process PDFs on external servers to fully native apps built on Apex and Lightning that generate PDFs entirely inside your Salesforce trust boundary.

The most important decision when choosing how to generate PDFs from Salesforce is whether the tool processes documents inside your org or routes data to an external server.

Integration-based PDF generation works by extracting data from your Salesforce org via API, sending it to the tool’s own cloud server, generating the PDF there, and returning it to Salesforce. Every time a user generates a PDF, your CRM data leaves your Salesforce security boundary. For teams in regulated industries, this creates compliance exposure. For all teams, it creates an integration dependency that breaks every time Salesforce releases a major update.

Native PDF generation runs entirely inside your Salesforce org using Apex. The data never leaves the platform. The PDF is generated inside your org and stored as a Salesforce File attached to the originating record. Field-level security applies automatically because the generation process runs as the triggering Salesforce user, with full respect for your sharing rules and permission sets.

Generating a PDF from a Salesforce record follows six steps: install a document generation app, build a PDF template, connect it to a Salesforce object, add a generation button, generate and verify the PDF, then distribute or send for signature. Most teams complete their first working PDF generation within a few hours of setup.

Manual PDF generation works well for individual records. For recurring, high-volume PDF creation, automation through Salesforce Flow eliminates manual triggers entirely.

A record-triggered Flow fires when a specific condition is met on a Salesforce record: an Opportunity moved to Closed Won, a contract record approved, an invoice record created, a case marked resolved. The Flow calls the document generation action as one of its steps, passing the template ID and the record ID. The PDF generates, attaches to the record, and the Flow continues with the next steps — emailing the PDF to the client, sending a notification, or triggering a signing workflow.

For recurring batch PDF generation — monthly invoice runs, quarterly renewal notices, annual compliance letters — a scheduled Flow fires at a set time. It queries the relevant records, loops through each one, and triggers PDF generation for the entire batch. The PDFs generate asynchronously so the Flow does not time out on large batches.

Bulk PDF generation from a list view is the manual version of batch generation. Select multiple records from a list view, click the bulk generation button, choose the template, and confirm. The tool generates a separate PDF for each selected record using that record’s live Salesforce data, and attaches each PDF to the correct record automatically.

A batch of 200 invoices that would take hours to produce one at a time typically completes in a few minutes of background processing. Bulk list view generation does not require any admin configuration beyond the initial template setup. Any user with the generate documents permission can run a bulk generation job from any list view the template is associated with.

For a detailed look at how bulk generation works and the time it saves at scale, see our guide on bulk document generation in Salesforce.

The quality of the generated PDF depends on both the template quality and the generation method.

Formatting fidelity. Native tools that generate PDFs inside Salesforce using Apex-based rendering produce more consistent formatting than integration-based tools that rely on external conversion services. Complex layouts with headers, footers, multi-column sections, and precise image positioning render more accurately with native generation.

Font embedding. When building Word-based templates, use fonts that are standard or widely available. Unusual fonts that are not embedded in the PDF may render incorrectly on the recipient’s device. System fonts like Calibri, Arial, and Times New Roman are safe choices.

Image resolution. Logos and images in PDF templates should be high resolution but optimised in file size. A 300 DPI PNG or vector SVG produces a sharp logo. A low-resolution JPEG produces a blurry one. Large unoptimised images slow PDF generation and produce oversized output files.

With a native document generation tool, generated PDFs are stored as Salesforce Files on the record they were generated from. Every PDF is accessible from the Files related list on the record, searchable in Salesforce, and subject to your existing record access and sharing settings.

No manual file management is required. The PDF does not need to be downloaded, renamed, and re-uploaded. It is already in Salesforce, already named correctly using the naming convention configured in the template, and already associated with the correct record.

For teams that also need PDFs stored in external systems — Google Drive, OneDrive, Dropbox, or SharePoint — native document generation tools with a storage connector can push generated PDFs to those locations simultaneously while keeping a copy in Salesforce. Dochly Storage supports Google Drive, OneDrive, and Dropbox connectors that sync generated documents automatically without any manual export step.