Skip to main content

Known Limitations

This page lists current limitations in Document Studio (Viewer), with short notes on impact and practical handling.

note

Use this page during planning and implementation to avoid surprises in production.

Before you go live

Review these limitations before rolling Viewer out to end users, especially if your implementation includes large templates, automation, or strict compliance requirements.

Quick list​

  1. Limited file format support
  2. File size restrictions
  3. Image size restrictions
  4. Incompatibility with certain devices
  5. No real-time editing
  6. Limited customization options
  7. Security and privacy concerns (Office Preview)
  8. Limited integration capabilities
  9. Potential performance issues with large documents
  10. Document 30-second timeout
  11. Limited offline access

1) Limited file format support​

Viewer supports common formats, but less common types (for example .odt, .pub) may not be handled consistently.

Impact: Some files may require conversion before viewing.

Recommendation: Standardize on supported file types where possible.

2) File size restrictions​

Very large files can be difficult to open or process.

Impact: You may need to reduce file size or split the document.

Recommendation: Use smaller source files and avoid overly heavy document payloads.

3) Image size restrictions​

High-resolution images may not render optimally in all cases.

Impact: Large images can affect readability and output quality.

Recommendation: Optimize and compress images before using them in templates.

4) Incompatibility with certain devices​

Experience may vary by device, OS, or browser.

Impact: Some users may see different behavior depending on their environment.

Recommendation: Validate key use cases on the browsers and devices used by your team.

5) No real-time editing​

Viewer is focused on viewing/generation, not collaborative real-time editing.

Impact: Real-time edits should be done in a separate editing tool.

6) Limited customization options​

UI/view customization is intentionally limited.

Impact: Personalized viewing layouts may not be available for all use cases.

7) Security and privacy concerns — Office Preview​

When using Office Preview, some organizations may have stricter privacy requirements.

Impact: Security-sensitive teams should review their internal policy before enabling this mode.

Office Preview review

If your organization has strict privacy, residency, or compliance requirements, review Office Preview usage with your internal security team before enabling it.

8) Limited integration capabilities​

Integration coverage may not match every external tool or workflow.

Impact: Some processes may require additional automation steps.

Recommendation: Plan for Flow, Apex, or supporting automation where needed.

9) Potential performance issues with large documents​

Complex or large documents can load more slowly.

Impact: Users may experience slower response times.

Recommendation: Keep templates as simple as possible and reduce heavy content where feasible.

10) Document 30-second timeout​

Document creation has a 30-second timeout limit.

Factors that affect completion time include:

  • Template complexity
  • Number of data items
  • Size of data items

Impact: Complex generations may time out.

Timeout planning

If your generation process is complex, test with real production-like data early and consider simplifying the template or generation scope.

11) Limited offline access​

Viewer requires an active connection for normal usage.

Impact: Offline viewing/editing is limited.

Need help?​

If you need help choosing the right implementation approach for these constraints, contact support.

More resources​