How to Export an Experience as a PDF

This guide shows you how to style an Experience for print, generate a PDF in a Flow, and return that PDF to the user as a browser download.

Prerequisites

• Access to a Space where you can edit Experiences and Flows
• PDF export and print media states turned on for your Space. If you can't find them, contact your administrator.

• One of the following:

  • the Flow runs with a user-backed Space identity (for example, triggered by a signed-in Ligantic user — the built-in USER and ADMIN roles qualify), or
  • the Space has a guest auth strategy

When the Flow has a user-backed Space identity, the PDF renders with that user's access — the Experience does not need to be publicly accessible, and built-in USER/ADMIN roles can export any Experience in the Space. Identities not backed by a user (guest or magic-link sessions) render anonymously and require a guest auth strategy.

Configure Print Styling

1. Open the target Experience in the Experience designer.
2. Select a block you want to style for print.
3. In the block state editor, add or select the Print media state (see Experience States and Print Layout).

4. In layout settings for that state:

   • Set Display to none to hide blocks in printed/PDF output.
   • Set Break Before, Break After, and Break Inside when you need pagination control.
5. Repeat for headers, controls, or decorative blocks you do not want in exported PDFs.

Note: Setting Display to none removes the block from the printed page, and it takes no space.

Preview Print in the Experience Designer Canvas

1. Use the canvas media selector.
2. Select Print.

3. Confirm print-specific styles:

   • Hidden blocks disappear from the canvas.
   • The layers tree shows hidden-in-view blocks with reduced opacity and a closed-eye icon.
   • Page layout is constrained to print width with a page boundary guide.

If needed, also preview responsive breakpoints with Small <768px and Large >=1200px.

Build the Export Flow

Create a Flow with these nodes:

1. Flow - Trigger (flow:trigger)
2. Experience - Pdf - Create (experience:pdf:create)
3. UX - Action (ux:action) configured as download

Configure Experience - Pdf - Create:

• Experience: the Experience to render
• File Name: optional output name (defaults to <experienceName>.pdf)
• Format: A4, Letter, or Legal
• Orientation: Portrait or Landscape
• Margins / Scale / Header / Footer: optional print settings
• Timeout (seconds): default 30

Configure UX - Action:

• Action: Download
• Connect experience:pdf:create file output to the UX - Action files input handle

Connect control handles:

• trigger -> experience:pdf:create.trigger
• experience:pdf:create.success -> ux:action.trigger

Trigger the Flow From a Button

1. In the Experience, select a Button block.
2. Configure the Button block's action as a Flow trigger.
3. Select your export Flow and trigger node.
4. Publish changes.
5. Run the Experience and click the Button block.

Result: The Flow renders the Experience in print mode, creates a PDF file, and the client downloads it.

Troubleshooting

Experience - Pdf - Create Takes the Error Path Immediately

• Confirm experienceId is set and the Experience has a published path.

Auth-Related PDF Render Failure

• If the Flow is triggered without a user-backed identity (for example, a guest or magic-link session), confirm the Space has a guest auth strategy.
• Confirm the guest strategy's default role has read access to the target Experience; without it the render returns not-found.

Download Action Does Not Download a File

• Confirm ux:action is set to download.
• Confirm the files input handle receives a valid file entry from experience:pdf:create.file.