You are here:
Client-Side and Server-Side Document Generation in CLM Compared
Client-Side document generation is better for some use cases, and Server-Side document generation is better for others. A table summarizes the factors to consider.
Server-Side document generation is only supported in customer orgs and it isn't enabled by default. To enable this feature, see Enable Server-Side Document Generation Setting for the Salesforce Industries Package.
Client-Side | Server-Side |
|---|---|
Best for synchronous use cases that generate documents within a process flow. |
Best for asynchronous use cases that include a polling mechanism. |
Best for documents with less than 200 quote lines, contract lines, rate sheet lines, and so on. |
Best for documents with lots of token processing, heavy tabulation, or more than 200 line items. |
Best for lightweight documents that don't overload web browser resources. |
Best for generating large batches of documents. |
Best for on-demand generation and point solutions. |
Best for trigger-based document generation, such as generating documents based on a Case status change. |
Supports default, extended, and custom fonts. For more information, Fonts for Client-Side Document Generation in CLM. |
Supports only specific default fonts. For more information, Fonts for Server-Side Document Generation. |
Includes multi-language support. |
Doesn't include multi-language support. |
Supports web, DOCX, and PPTX templates. |
Supports DOCX and PPTX templates. |
Supports Customer Community Plus, Customer Community, and Partner Community users to generate documents using client-side Omniscripts. For more information, see CLM Omniscripts Overview. |
Supports Customer Community Plus, Customer Community, and Partner Community users to generate documents using the singleDocxServersideLwc server-side Omniscript. For more information, see Using the docGenerationSample/singleDocxServersideLwc Omniscript. |
These limits apply for Client-Side and Server-Side document generation:
Client-Side | Server-Side |
|---|---|
Content Version daily limit: The generated documents are stored in Salesforce Content. Each org type has a daily limit (per 24 hours) on how many .docx and .pdf documents can be generated and stored. For more information, see Content Version Limit. |
Content Version daily limit: The generated documents are stored in Salesforce Content. Each org type has a daily limit (per 24 hours) on how many .docx and .pdf documents can be generated and stored. For more information, see Content Version Limit. |
File Storage limit: The org’s file storage limit is calculated by a base allocation. It’s based on your Salesforce org edition plus a per-user allocation multiplied by the number of standard licensed users in the organization. For more information, see File Storage Limit. |
File Storage limit: The org’s file storage limit is calculated by a base allocation. It’s based on your Salesforce org edition plus a per-user allocation multiplied by the number of standard licensed users in the organization. For more information, see File Storage Limit. |
Size limit: The size limit for client-side generated documents is 10 MB, while guest users can only generate documents up to 2 MB starting Winter '22 release. For earlier releases, the size limit is 2 MB.  Note
For document reconciliation, the size-limit is 4 MB. |
Size limit: The size limit of server-side generated documents is 2 MB. You can submit up to 1000 requests per hour, per org. |
