PrintLatch v0.1.1 is out Windows 11 x64 · Apache-2.0

Local print infrastructure for web developers

From web app
to printer. One local latch.

PrintLatch gives an explicitly authorized web app or Node.js process a narrow path to printers already installed in Windows. Its local dashboard detects targets and verifies a PDF capture before any optional physical test. No print cloud. No account. No silent jobs.

Download for Windows View on GitHub
Windows 11 x64 PDF only Unsigned v0.1
PrintLatch Agent Agent online

Local queue

Print jobs

All 3 Active 1 Finished 2 ⌕ Search jobs
invoice-1048.pdf billing.example · 2 pages
Printing
packing-slip-083.pdf warehouse.example · 1 page
Succeeded*
preview.pdf local process · 3 pages
Preview

* Succeeded means Windows accepted the submission. Physical output is not claimed.

Windows devices

Printers

Scanned locally · just now
PrintLatch PDF CaptureBuilt-in · verified
Ready
Microsoft Print to PDFWindows installed
Discovered
Office printerWindows installed
Discovered
Adobe PDFWindows installed
Discovered
Discovery is not a paper-output claim. The installed Windows driver owns the physical print path.

Authorization

Pair one origin

No wildcard access
ONE-TIME PAIRING CODE PL-••••••••-••••••••
Expires in 04:59

Created locally and consumed once.

01

Exact originhttps://billing.example only

02

Scoped tokenRotatable and expiring

03

Local consentNo silent remote pairing

Actual product model

Queue state, target, source, and limits stay visible.

01Loopback only

No LAN listener and no PrintLatch relay.

02Explicit pairing

One exact HTTPS origin at a time.

03Durable queue

Visible state without silent replay.

04Zero telemetry

Your documents stay on your machine.

/ THE GAP

A boring problem,
kept boring.

Your app already creates the PDF. Windows already knows the printer. The missing piece is a small, authorized connection between them.

PrintLatch does not replace drivers or become another cloud platform. It accepts one constrained document, records one local job, and hands it to one explicit target.

Web app PrintLatch Windows queue Installed printer
/ SECURITY MODEL
Read the threat model

Local does not mean
unauthenticated.

Every print, preview, document, queue, cancel, and retry operation requires a scoped credential. Browser access starts with a person at the Windows machine.

01ORIGIN PAIRING

Nothing prints before local consent.

A 128-bit, five-minute code is bound to one exact HTTPS origin and consumed once.

https://billing.examplePaired
https://anything-else.example Blocked
02NETWORK

One machine.
No cloud hop.

127.0.0.1LOCAL

The API binds to loopback. It is not a LAN print server.

03DOCUMENT GUARD
PDF VALID

PDF in.
Surprises out.

MIME, signature, pages, objects, streams, images, encryption, and active features are checked before queueing.

≤ 10 MiB≤ 100 pages
04QUEUE SAFETY

Interrupted is not repeated.

If Windows submission is interrupted, the job becomes unknown. It is never replayed automatically.

queued printing unknown manual decision
/ HOW IT WORKS

Three deliberate steps.
No invisible fourth.

The bridge stays short enough to understand, test, and remove.

  1. 01

    Open the local dashboard

    Create a five-minute grant bound to the exact loopback dashboard origin.

    printlatch dashboard
  2. 02

    Detect and preview

    See what Windows reports, then validate and inspect the built-in static test PDF.

    nothing printed yet
  3. 03

    Confirm one safe capture

    Write a local PDF artifact, observe the real queue state, then integrate a client.

    printerId: "capture:pdf"
/ HONEST V1 SCOPE

Small enough
to trust.

V1 is for invoices, packing slips, and internal document automation on one Windows machine. The built-in PDF capture path is verifiable without printer hardware.

PrintLatch v0.1DOES
  • 01Run on Windows 11 x64
  • 02Accept static, unencrypted PDFs
  • 03Support A4 and Letter document workflows
  • 04Pair exact HTTPS browser origins
  • 05Serve local Node.js 20+ processes
  • 06Capture PDFs for end-to-end testing
  • 07Discover Windows-installed printers
PrintLatch v0.1DOES NOT
  • 01Support macOS, Linux, ARM64, or Windows 10
  • 02Send raw ESC/POS or ZPL
  • 03Guarantee label or receipt media
  • 04Accept HTML, images, ZIPs, or encrypted PDFs
  • 05Relay jobs through a PrintLatch cloud
  • 06Manage remote printer fleets
  • 07Prove that physical paper emerged
One more honest limit:

The v0.1 Windows binary is unsigned and may trigger SmartScreen. Verify the published SHA-256 checksum before running it. No build attestation is claimed for v0.1.1.

/ TYPESCRIPT SDK

One explicit job.
Nothing magical.

The dependency-free SDK only accepts a loopback HTTP base URL. Local-process tokens stay in server or desktop code, never in a browser bundle.

Explore the HTTP API
print-invoice.mjs Node.js 20+ 
const client = new PrintLatchClient({
  token: process.env.PRINTLATCH_TOKEN,
});

const job = await client.createJob({
  pdf,
  mode: "print",
  printerId: "capture:pdf",
});

console.log(job.state); // queued
Job accepted locallyPL-1048

Apache-2.0 · No account · No telemetry

Test the whole path.
Keep the PDF local.

Get PrintLatch Read installation guide