Skip to content
PLIEGObooklet studio

Local architecture

Your document is worked on here

What Pliego processes in the browser, what it never stores, and which normal requests reach the host.
Tool→Your document is worked on hereLeer en español
01

You choose

The browser gets access only to the file you explicitly choose.

→
02

Processed in memory

Local PDF.js and pdf-lib validate, compose, and draw the result.

→
03

You download

The browser creates a temporary file and saves it where you choose.

Pliego does not have

The PDF is not sent or stored.

The document and output live in tab memory. Resetting, replacing, or closing discards the job and revokes temporary URLs. We use cookieless Cloudflare Web Analytics for aggregated navigation and performance statistics. We do not send your PDF, its name, content, page count, or document metadata to analytics. Navigation and performance requests are separate from the document's local processing.

Hosting can still see

Normal web requests.

To serve HTML, CSS, JavaScript, favicon, and worker, the host processes IP, headers, and logs under its platform terms. Vercel previews may inject its toolbar. Those requests do not contain the selected PDF.

Limits

10 MiB · 80 pages

Password-free. Forms, signatures, links, and actions are not copied. Mixed sizes are fitted with margins; always inspect the output.

Keep learning

Three guides, one physical test.

01Print a booklet

From reading order to sheets, folding, and staples.

↗
02Manual duplex without guessing

Mark one sheet, test reinsertion, and correct its rotation.

↗
03Blank pages and multiples of four

Where blanks land in 6, 10, and 14-page documents.

↗

A test costs one sheet. Guessing can cost the whole job.

Open the tool →