BroadPaper

Structured, not chaotic

Page → Section → Row → Columns → Blocks. Predictable layouts that paginate deterministically instead of a free-form canvas that produces garbage.

One template, any brand

Templates reference theme tokens. Render the same saved JSON as Brand A, Brand B or a white-label customer with a single option change.

No browser required

A WebAssembly layout engine renders vector PDFs with selectable text — in Node, on the edge, or in the user's own browser. Chromium stays available as the fidelity reference.

What you see is what breaks

BroadPaper owns pagination — keep together, orphans and widows, repeated table headers. Point the canvas at the same engine as the PDF and a page break on screen is a page break in the file.

Data stays yours

Schemas in, JSON template out. Runtime data is bound in your browser or your own renderer. BroadPaper makes no calls of its own.

Custom blocks, first class

Register your own blocks with a declarative inspector and a pure render function. They drag, drop, bind, theme, preview and print like the built-ins.

Safe by design

A constrained expression language with no eval, a structured rich-text model instead of HTML, URL validation and SSRF-guarded asset fetching.

Built to be embedded

A framework-agnostic core with thin React and Angular wrappers, a versioned and migratable document format, feature flags for commercial tiering, and no global styles.

See it before you read about it

Run the demo — a Client Investment Review across three brands, with a custom block and PDF export rendered in the browser. No account, no server, nothing to install.

Preview mode showing the report exactly as the PDF will contain it — Preview mode draws what the PDF draws, page for page.

Page one of the example PDF: cover, adviser summary and a portfolio value chart — The PDF it produced — four pages, selectable text, vector charts.

Where to start

Embedding it. Quick start gets a designer on screen with your own data in about thirty lines, and every example on that page is complete enough to paste and run. Then React or Angular for the wrapper you are actually using, and Events & API for driving it from the outside.

Understanding it. Core concepts explains the document model and why it is a structured tree rather than a canvas. Document schema is the JSON your users will be saving.

Using it. Using the designer is the authoring surface — placing blocks, binding data by typing {{, and controlling where pages break. Worth reading once even if you are only embedding it.

Feeding it. Data sources is your side of the contract, and Dynamic bindings is the expression language your users will bind with. Then Conditions, Repeaters, Tables and Charts.

Branding it. Themes is how one template renders as three brands, and White labelling is how it stops looking like ours.

Shipping it. Browserless PDF is the recommended renderer and the one that needs no server. Chromium PDF service is the alternative, and that page compares what each one guarantees. Validation, Security and Migration & versioning are what you will want before it meets real customers.

Extending it. Custom blocks — your own blocks, with a declarative inspector and a pure render function, no fork required.

BroadPaperStop building custom report designers.