Generate PDFs and Word docs from any Salesforce record. Merge PDFs, add barcodes and QR codes, compute totals — 100% native, zero external dependencies, 100% free forever. All features, all users, no paid tiers. PowerPoint and Excel coming soon.

Join the Community Channel | Website | Roadmap

sf package install --package 04tal000006PhBBAA0 --wait 10 --target-org <your-org>

Install in Production | Install in Sandbox

Then: Assign DocGen Admin permission set | Enable Blob.toPdf() Release Update | Open the DocGen app

1. Create a template — pick Word, Excel, or PowerPoint. Choose your Salesforce object.
2. Select your fields — use the visual query builder, or paste a full SOQL statement for complex nested relationships.
3. Add tags and upload — type {Name} where you want data. Upload the file.
4. Generate — from any record page, in bulk, or from a Flow.

Download example templates from portwoodglobalsolutions.com.

Word is the most capable — it's the only format that supports images, barcodes, QR codes, rich text, and PDF output.

Place these outside the loop to compute totals from child records:

Store a ContentVersion ID (starts with 068) in a text field, then use {%FieldName} in your template:

Images work in both PDF and DOCX output. You can also embed images directly in your Word template — they render in PDFs automatically.

Rich text fields render with full formatting (bold, italic, lists, images) in PDF output. Images inside rich text fields work in PDFs. For DOCX output, use {%FieldName} image tags instead of rich text images.

PDF output only. No external services required.

To repeat rows inside a table (not the whole table), put the loop tags in the data row:

The {#Contacts} goes in the first cell and {/Contacts} goes in the last cell of the same row. The header row stays fixed, and the data row repeats for each record.

• Title pages — If your Word template has "Different First Page" enabled, the PDF will suppress headers and footers on page 1. Your cover page stays clean.
• Section breaks — Section breaks in your Word template create proper page breaks in the PDF.

Put a page break inside a loop to give each child record its own page:

{#Opportunities}
Customer: {Account.Name}
Amount:   {Amount:currency}
                              ← page break here (Insert → Page Break in Word)
{/Opportunities}

Five ways to combine PDFs:

Records with 2,000 to 50,000+ child records are detected automatically. Same template, same button — the engine handles pagination and async processing behind the scenes.

The query builder accepts full SOQL statements with unlimited nesting depth. Paste a query like:

SELECT Name, Industry,
    (SELECT FirstName, LastName, Account.Name FROM Contacts),
    (SELECT Name, Amount,
        (SELECT Quantity, Product2.Name FROM OpportunityLineItems)
    FROM Opportunities WHERE StageName = 'Closed Won')
FROM Account

The builder parses the query, displays the field tree with parent lookups highlighted, and generates copy-paste merge tags for your template. Outer SELECT / FROM clauses are stripped automatically — DocGen always runs against a specific record.

Tips:

• Test your query in Developer Console or tools like Salesforce Inspector before pasting.
• Use AI to help build complex queries — Agentforce, ChatGPT, Gemini, and Claude can all generate valid SOQL with nested relationships.
• Subqueries support WHERE, ORDER BY, and LIMIT clauses.
• Parent lookups (e.g., Account.Name, Product2.Family) work at every nesting level.

Generate documents for hundreds of records at once. Enter a filter condition, click Submit. Real-time progress tracking in the app.

Salesforce's PDF engine supports these fonts:

Custom fonts from your Word template (Calibri, Cambria, branded typefaces) fall back to Helvetica in PDF output. If custom fonts matter, generate as DOCX — Word preserves the original fonts.

Starting with Spring '26, the renderer supports expanded multibyte character rendering for international scripts.

These are Salesforce platform limitations, not DocGen bugs:

Template (.docx/.xlsx/.pptx)
    ↓
Decompress → Merge XML tags → Recompress
    ↓                              ↓
  DOCX/XLSX/PPTX              PDF path:
  (client-side ZIP)     DocGenHtmlRenderer → Blob.toPdf()

DocGen ships on a biweekly release cycle. Next release: April 17, 2026.

See CHANGELOG.md for full version history.

DocGen is 100% free, open source, and community-driven. Published through Portwood Global Solutions.

Need dedicated support? Contact us at [email protected].

We welcome contributions — see CONTRIBUTING.md for setup instructions.

We run the Salesforce Code Analyzer with Security + AppExchange rule selectors on every release. The current scan reports 51 High-severity SFGE ApexFlsViolation findings — all on package-internal custom objects. We believe in full transparency, so here they are:

Why these exist: DocGen is a managed package with the portwoodglobal namespace. Salesforce's USER_MODE keyword (which SFGE requires for compliance) breaks namespace resolution during managed package builds — field names like Query_Config__c fail with "No such column" because the SOQL engine requires the fully-qualified portwoodglobal__Query_Config__c. Since namespace-qualified field names don't compile in development scratch orgs, SYSTEM_MODE is the only viable option for package-internal objects. This is standard practice for managed packages on the Salesforce platform.

Salesforce's own AppExchange security review guidance explicitly states that bypassing CRUD/FLS is acceptable for "custom objects or fields like logs or system metadata that shouldn't be directly accessible to the user via CRUD/FLS." All DocGen custom objects fall into this category.

How access is actually enforced:

• Object-level CRUD: Enforced by DocGen_Admin and DocGen_User permission sets (platform-level)
• Field-level security: Enforced by the same permission sets (platform-level)
• Record-level sharing: All Apex classes use with sharing (platform-enforced)
• Standard objects (ContentVersion, ContentDocumentLink): Use USER_MODE + Security.stripInaccessible() (code-enforced)

No user can read, create, update, or delete any DocGen data without an explicitly assigned permission set.

Found a vulnerability? See SECURITY.md.

We maintain a beta channel for users who want early access to security hardening and new features before they're promoted to production. Beta packages can only be installed in sandboxes and scratch orgs.

sf package install --package 04tal000006PhG1AAK --wait 10 --target-org <your-sandbox>

Install Beta in Sandbox

Current beta (v1.26.0) includes:

• Everything in v1.25.0 (stable)
• Schema-based allowlisting for all dynamic SOQL queries (SOQL injection hardening)
• validateObjectName() and validateFieldList() enforce that all dynamic values in queries are validated against Schema.getGlobalDescribe() before execution

Once the beta passes Checkmarx re-scan and additional hardening (CSRF, DML bulkification), it will be promoted to a stable release.

Apache License, Version 2.0. See LICENSE.

Built by Portwood Global Solutions