Grouping, charts, barcodes, rich text, expressions, right-to-left layout, and a measured page stack are outside v1.

Give the attachment its moment.

Your app does the work. The report carries it forward. Open-source, flow-based documents from JSON to HTML and PDF.

Two JSON files. One useful attachment.

A header, a body that flows, and a footer. Save the layout as JSON.

Keep the values separate. Bind property paths, format fields, and populate tables.

.NET compiles self-contained HTML. Playwright prints the same document to PDF.

Three real reports. Synthetic data. Working downloads.

Line items, quantities, currency, and a total. The everyday attachment, done clearly.

Dates, activity, and a running balance. A month of transactions in one readable document.

SKUs, boxes, and quantities. The list that keeps the handoff organized.

The Windows builder puts blocks on the left, the preview in the middle, and properties on the right.

Illustrative view of the Windows report builder.

A focused v1 for documents that flow. Here is what the source actually does.

Text, fields, images, spacers, columns, and tables. Tables split by row; their headings repeat when printed.

A separate JSON data object binds on the .NET side. The compiler produces HTML; the exporter produces PDF.

MIT-licensed source. A Windows builder, a Blazor viewer, and a Next.js display sample.

A few useful answers, including the boundaries.

Is See Attached open source?

Does a report repeat its header on every page?

Can I use it with Blazor or Next.js?

What is outside v1?

Take the source. Define the layout. Give your data a document worth opening.

Want to look around first? Explore the examples