Since adjusting signature box sizes isn't currently supported, what are the best ways to format and align signature placeholders to keep them compact and prevent them from spilling over onto an extra page in the generated PDF?

Published on October 3, 2026 DRTE

Because server-side PDF page generation depends on total vertical content height (especially when dynamic tables like line items expand), signature blocks stacked vertically at the end of a document can sometimes get pushed onto a new page.

You can prevent awkward page splits and keep your signature block compact using three layout techniques within the DRTE Editor:

Strategy 1: Align Signatures Side-by-Side in an HTML Table (Best for Compact Layouts)

Instead of stacking [Signature1] and [Signature2] vertically, place them in a 2-column, borderless HTML table to reduce vertical height by 50%.

Strategy 2: Trim Vertical White Space & Paragraph Margins

Remove Extra Breaks: Delete empty <p><br></p> tags or excess line breaks directly above and between signature blocks.
Tag Integrity: Keep each placeholder tag (e.g., [Signature1] or [date[Signed Date]:[Signature1]]) intact within a single HTML tag block rather than splitting formatting across brackets.

Strategy 3: Enforce a Dedicated Signature Page via CSS Page Break

If your document content varies in length (e.g., invoices or SOWs with variable line items), attempting to fit signatures on Page 1 may cause unpredictable page cuts. The best practice is to force the entire closing/signature section onto a dedicated final page so both signatures stay together.

How to implement:

Open the Doc Section containing the signature block.
Click the Update HTML Content Source action button in the section header.
Inject class="page-break-before-always" into the first opening container tag (<p> or <div>):
Result: The server-side rendering engine automatically pushes the consent statement and both signature blocks together onto a clean, dedicated final page.

Knowledge Article Number: KA-00442