Generate test PDFs in your browser

A focused tool for generating test PDF files used in upload-flow QA, document-pipeline testing and viewer compatibility checks. Four profiles (lorem-ipsum body text, multi-page with sections and footer, a wide table of rows × columns, fully blank pages) at standard paper sizes A4, Letter, Legal, A3. PDF metadata (title, author, subject, creator) is populated so your parser sees realistic input.

How to use

Pick a content profile — lipsum / multi-page / big-table / blank.

Pick page count and paper size. Set a custom document title.

Hit Generate — the PDF is built with pdf-lib in your browser and saved to your device.

Lipsum, multi-page, table or blank — A4 / Letter / Legal / A3

Content profile

Pages

Paper size

Document title

PDFs are generated in your browser via pdf-lib — the file is saved straight to your device.

Features

Four content profiles — lorem ipsum, multi-page sections, big table, blank Four paper sizes — A4, Letter, Legal, A3 1 to 500 pages per document — exercise paginators and viewer scroll Real PDF metadata — title, author, subject, creator embedded

Frequently Asked Questions

Can I generate PDF/A or tagged PDF here?

Not via pdf-lib — those flavours need a stricter authoring path (XMP metadata, ICC profile, structure tree, explicit conformance). For PDF/A archival testing use a real PDF/A authoring tool or our compress-pdf / merge-pdf tools, which preserve PDF/A if the input was already PDF/A.

Why is the file so small for many pages?

The generated PDFs use only standard 14 fonts (Helvetica, etc.) — no font subset is embedded. That makes 100-page test files <500 KB. For tests against real production PDFs the absolute size will differ; that is fine if you are testing pagination or upload flows, less so if you are stress-testing memory.

Do these PDFs contain images or forms?

Not currently — they are vector-text-only. For PDFs with images, fillable forms or signatures use a dedicated authoring tool, or scan a real document. We deliberately keep this tool to text-based pipeline-test content.

Why does the big-table profile cap at one page per copy?

The big-table profile fills one full page with 20 rows × 5 columns. If you set Pages = 3, you get three identical-content pages. The goal is to test table renderers / extractors, not produce a 100-row spanning table — for that use a real CSV export to PDF.

💡 Want us to improve this tool just for you?

We can — and it's free! Just send us a quick message with your idea. If you'd like to discuss it in detail, leave your email and we'll get back to you. You can stay anonymous.

How do you rate this tool?

Thank you for your rating!

Change my rating

Want to leave a comment?

Want to share more? Leave a comment!

Thank you! Your comment will appear after moderation.

Who is this tool for?

Published 21 May 2026