PDF Deliverable Assembly Kit

Combine, reorder, rotate, omit, and label pages from local PDFs into one verified deliverable and exact assembly manifest.

Consultants, agencies, legal teams, and operators preparing a final client-ready PDF packet.

Local PDF files (1–10, 50 MB total)

Selecting files creates a page plan in file/page order. Edit the JSON to reorder, omit, rotate, or label pages. Removal is omission.

Assembly plan JSON

{
  "sources": [
    {
      "bytes": 120000,
      "id": "proposal-main",
      "mime": "application/pdf",
      "name": "proposal.pdf",
      "page_count": 2
    },
    {
      "bytes": 80000,
      "id": "appendix-main",
      "mime": "application/pdf",
      "name": "appendix.pdf",
      "page_count": 1
    }
  ],
  "pages": [
    {
      "label": "Cover",
      "rotation": 0,
      "source_id": "proposal-main",
      "source_page": 1
    },
    {
      "label": "Appendix A",
      "rotation": 90,
      "source_id": "appendix-main",
      "source_page": 1
    },
    {
      "label": null,
      "rotation": 0,
      "source_id": "proposal-main",
      "source_page": 2
    }
  ],
  "metadata_policy": "replace",
  "metadata": {
    "title": "Client deliverable"
  },
  "output_filename": "client-deliverable.pdf",
  "limits": {
    "max_output_bytes": 50000000,
    "max_output_pages": 500,
    "max_source_bytes": 50000000,
    "max_source_files": 10,
    "max_source_pages": 500,
    "max_total_source_bytes": 50000000
  }
}

Verified result

Metadata and trust policy

Hosted direct, API, and MCP output is metadata-plan-only and never claims bytes, digest, or PDF verification. Actual generation requires local Files in the browser.
Encrypted or password-protected, MIME-mismatched, malformed, oversized, page-count-mismatched, or unsupported PDFs fail with typed non-reflective errors. No password input or decryption bypass is available.
Removal is explicit omission from the output page list. Safe labels are embedded as Unicode PDF page-label prefixes and are also retained in the exact page-source map and receipt; they are not drawn over source page content.
Metadata behavior is explicit: preserve copies title, author, subject, and keywords from the first selected source; remove clears all four; replace clears author, subject, and keywords and writes only the submitted safe title. Every policy sets creator and producer to the Utilito kit identity and creation/modification dates to the Unix epoch for deterministic output.
Downloads occur only on explicit clicks. Blob URLs are published atomically and revoked on replacement, invalidation, failure, and pagehide. Nothing is uploaded, stored, auto-downloaded, signed, or deployed.