S-Docs Limitations

General limitations of S-Docs Capabilities:

  • S-Docs runs on the Salesforce Platform and is bound by all Execution Governors and Limits placed on the Salesforce platform. These limits have been known to change with each Salesforce release and can have a wide impact on S-Docs that results in errors when generating and viewing S-Docs. Those errors can appear if the generated document:
    • Is too many pages long, too large in terms of file size, too complex in terms of logic within a template, takes an extended amount of server time to generate, requires too many database queries, database queries take too long to execute and a wide variety of other causes.
  • S-Docs typically supports at least 200 records for mass merge (batch processing). The upper limit is driven by Salesforce governor limits and is dependent on your template's complexity.
  • Salesforce Execution Governors also affect emails, notifications, and processes that S-Docs may run. Please visit this link for a complete and updated list of Salesforce Governor Limits.
  • S-Docs emails are subject to the following Salesforce email limitations.
  • Javascript and Dynamic CSS is not supported.

PDF Output:

When using the S-Docs rendering service for PDF output, please be aware of the following additional considerations and limitations:

  • The PDF rendering service renders PDF version 1.4
  • Fillable PDFs are not supported
  • Password-protected PDFs are not supported
  • The rendered PDF file either displays in the browser or is downloaded, depending on the browser’s settings. Specific behavior depends on the browser, version, and user settings, and is outside the control of S-Docs
  • If images outside of Salesforce are used in the S-Docs template directly, or dynamically through a merged image field, you must whitelist the URL domain (using Setup > Remote Site Settings) to avoid broken image icons in the PDF
  • The final document will render the markup and data, but it might not render formatting contained within the contents of rich text area fields, or image fields added to the template unless you specify them as containing markup
  • Long lines of text that don’t have break points likes spaces or dashes (such as long URLS) can’t be wrapped by the PDF rendering service and may “flow” off the side of the page, cutting it off. This can be fixed using the breakeverynchars attribute, which adds a line break after a specified number of characters.
  • PDF templates support CSS 2.1. Some CSS attributes, such as word-wrap, are CSS 3, and are therefore not supported
  • PDF rendering doesn’t support JavaScript-rendered content
  • Fonts supported (specified as font-family): Arial Unicode MS, sans-serif, serif, Times New Roman, and Courier. Web fonts and other fonts are not supported. S-Docs provides additional support for MICR fonts.
  • Bold, italicized, or underlined text is not supported in PDF files that use Unicode fonts (if you have selected template contains international characters)
  • If the PDF file fails to display all of the page’s text, particularly multibyte characters such as Japanese or accented international characters, make sure you check off Template contains international characters in the “Document Options” tab of the template editor. If merged field values are failing to render correctly, also set the “Unicode enforcement level” to Strict to override any font settings that are being applied to merged fields.
  • “Arial Unicode MS” is the only font supported for extended character sets that include multibyte characters
  • The maximum response size when creating a PDF file must be less than 15 MB
  • The maximum file size for a generated PDF file is 60 MB
  • The maximum total size of all images included in a generated PDF is 30 MB
  • PDF rendering doesn’t support images encoded in the data:URI scheme format


Note: Limitations to PDF files in general also apply to the PDF-Upload feature in addition to the limitations listed here.
  • PDF is the only file type supported
  • Pre-existing templates cannot be switched to the PFD-Upload template format
  • PDF-Upload templates cannot be switched to a different template format
  • The HeaderFooterPage Settings, and Create Salesforce Task tabs are not available
  • PDFs must be the traditional 8.5 x 11 inch size; landscape PDFs are not supported
  • The page count upper limit is currently around 15 pages. Keep in mind that certain contents increase template size and complexity (such as images or large amounts of text), which may have an effect on the page number limitation
  • To export templates and transfer them between orgs, use the S-Docs Template Migrator instead of manually exporting and importing the template data.
  • Component templates are not supported (however, you can use PDF-Upload templates as components in regular PDF templates)
  • Related Lists are not supported
  • Render statements need to be written out (the Insert Conditional Logic button is not supported)
  • Nested renders are not supported
  • Direct SOQL related lists are not supported

DOCX & PPTX Output:

Upper Limits

These limits are upper limits only; depending on the complexity of your document, you may run into limits on the file size or processing time well below these limits. Nonetheless, we estimate that at least 80% of DOCX/PPTX templates should be able to reach these upper limits. For DOCX templates that exceed these limits, other formats such as DOC can be used to fulfill your use case.

  • Your uploaded template has an upper limit of 10 related lists
  • Your uploaded template has an upper limit of 10 pages for DOCX and 10 slides for PPTX. Generated documents have an upper limit of 20 pages for DOCX and 20 slides for PPTX

What DOCX/PPTX supports without limitations:

  • Merge fields and merge field formatting like format-date, format-number, etc.
  • RENDER feature
  • Salesforce Lightning
  • Salesforce Console
  • Embedding images referenced via URL (e.g. images from rich text fields, or <img src=...>) into the DOCX/PPTX for documents generated on SDCreate3
  • Named queries
  • One-click and zero-click buttons
  • Email

What DOCX/PPTX supports, with limitations:

  • S-Doc Jobs
    • Documents generated via S-Docs Jobs must have a final size of less than ~120 KB
  • Mass merge batch document generation
    • For DOCX/PPTX templates less than ~120KB (same as the limitation on S-Doc Jobs)
  • Mass merge combine-all into single printable DOCX
    • Each document in a single printable DOCX/PPTX has a limitation of 120KB because those documents are generated by S-Docs Job. See the above limit
  • Embedding images referenced via URL (e.g. images from rich text fields, or <img src=...>) into the DOCX/PPTX for documents generated via SDBatch or S-Doc Jobs
    • Rich text image fields are fully supported if the document isn't generated using an S-Docs Job (via an S-Docs button). If they are generated via S-Doc Job, the ~120KB limit still applies per document
  • Runtime prompts
    • If your runtime prompt merge field result has rich text formatting, like bold red text, it won't show up in the final template
  • Related lists
    • Simpler related lists are supported, but more complex related list qualities like using <td> cells as column prefixes are currently not supported
  • Rich Text Fields
    • Line breaks, images, and ordered/unordered lists are retained. Note that if a list begins on line 1 of the rich text field, a blank line will be inserted above it. All other formatting (such as bold text and alignment) is removed
    • Fonts and font sizes will not be pulled from Salesforce rich text fields into your DOCX document - they will simply match Microsoft Word's "Normal" style. If you want your document to display the font from your rich text field, you can either change Microsoft Word's "Normal" style to match the desired font/font size, or use the font-family and font-size merge field attributes

What DOCX/PPTX does not support:

  • Generating DOCX/PPTX without creating an Attachment or File
  • The Live Edit feature
  • "Related To Type" of OpportunityLineItem, QuoteLineItem, or any other standard Salesforce object that does not support Notes & Attachments
    • We recommend using DOC for these objects
  • Percentages as units of measurement in images
    • However, absolute sizes (i.e. inches, centimeters, pixels) are fully supported


  • DOCX & PPTX limitations also apply to XLS/XLSX output.
  • XLS supports related lists, but not multiple sheets
  • Related lists are not currently supported for the output type XLSX
  • Size limitation: For very large, text-dense XLSX templates, you may hit a file size limitation.


Was this helpful?