Skip to content

Large Response and Diagram Handling

Aryeh Citron edited this page May 1, 2026 · 4 revisions

Note: This page covers diagram splitting — when a diagram has too many interactions to fit in a single image. For truncating or redacting content within individual diagram notes (wide tokens, large bodies, sensitive data), see Filtering and Redacting Diagram Content.

The library automatically handles large content using three splitting mechanisms:

Splitting Triggers

Trigger Threshold What it does
Encoded PlantUML length 2,000 characters (DefaultMaxEncodedDiagramLength) When the URL-encoded PlantUML exceeds this limit, the diagram is split to stay within PlantUML server URL length limits.
Response note size 15,000 characters (MaxResponseNoteChunkLength) Large response bodies are split across multiple diagram segments with "Continued From Previous Diagram" / "Continued On Next Diagram" markers.
Estimated diagram height 12,000 pixels (MaxEstimatedDiagramHeight) When the estimated rendered height exceeds this limit (calculated from arrow count × 45px + note lines × 18px), the diagram is split to prevent excessively tall images.

Additionally:

  • Long URLs exceeding 100 characters are wrapped across multiple lines in the diagram.
  • Lines exceeding 800 characters (MaxLineWidth) are wrapped to prevent rendering issues.

When a split occurs, the new diagram continues with the same participants and auto-numbered steps, maintaining visual continuity.

Home


Demo


Getting Started

Common Tasks

Integration Guides

Extensions

Configuration

Features

Reference

Clone this wiki locally