SelectPDF has two known limitations when used in Bubble. Both stem from how SelectPDF processes pages on its end — not from your app's configuration.
Content is cut off when using the Webkit rendering engine
The Webkit rendering engine in SelectPDF caps content at an arbitrary height, which causes PDF output to be cut off at the bottom. Webkit has also been deprecated in SelectPDF because it can't handle modern CSS and JavaScript. The Blink engine doesn't have this problem.
What you might notice:
PDF output is cut off partway down the page when using the Webkit rendering engine
The same content renders fully when using the Blink engine
Workaround: Switch to the Blink rendering engine in your SelectPDF workflow action. Webkit is deprecated and shouldn't be used for new PDF generation.
Dates display in the wrong timezone
When SelectPDF renders a PDF, it uses the timezone of the server environment that processes the export — not the timezone of the user who triggered the workflow or what's displayed in your app. Dates and times in the exported PDF may not match what users see on screen.
What you might notice:
Dates and times in a generated PDF appear offset from what's shown in the app
The difference corresponds to a timezone gap between the user's local time and the server's timezone
Workaround: Manually offset the date values passed to your PDF page. Add or subtract hours from the date expression to match the correct timezone before the PDF is rendered. The exact offset will depend on the user's timezone relative to the server.