Press-ready output, not a screenshot
Output is the same PDF you uploaded with the editable fields filled in. CMYK preserved, trim boxes preserved, spot colors preserved where the source supports it. Preflight on every render.
For print shops
Your shop already approved the artwork. StackFill turns that approved PDF into a customer-personalized link — CMYK-correct, trim-correct, no recreation in a new design tool.
Customer calls in: "Order the same cards as last time, but with my new title and four new reps." Someone in the shop opens the InDesign file, edits five names, five phone numbers, five emails, exports a press PDF, and prays nobody dropped a baseline shift.
The shops that have tried web-to-print platforms know the trap: the platform won't print the file you've already approved. It wants you to rebuild every business card, every letterhead, every postcard inside its editor first. So you stop using it and go back to editing files by hand.
The variant tax compounds:
Upload the press-ready PDF you already use. Click the fields a customer is allowed to change — name, title, phone, email, the four image slots on the photo card. Lock the logo, the layout, the spot color, the trim.
Hand the customer a hosted fill link, or have a developer add the embed to the storefront you already have. They personalize against a live proof over your locked artwork. The PDF they download is the same artwork — with their values in the editable fields — in CMYK, with your trim and bleed, ready to drop into your queue.
The shop touches the file once: upload, mark, save. Every reorder after that is the customer's job.
Output is the same PDF you uploaded with the editable fields filled in. CMYK preserved, trim boxes preserved, spot colors preserved where the source supports it. Preflight on every render.
Your approved InDesign or Illustrator export is the source. StackFill doesn't ask you to recreate the artwork. It just parses it and exposes the editable parts.
Email a link to a one-off customer. Or put the StackFill widget on the storefront you already run: it works on any storefront with a developer wiring in a few server calls, with no ready-made plugin yet. Same engine, same output.
One template feeds one customer at a time or, on Pro, a CSV of 200: same locked artwork, different field values, one PDF per row from one batch run.
Your foundry-licensed fonts upload once. Every template binds to the same library, so no more "wait, where's the right Helvetica?"
The customer fills out a clean form on their phone or laptop. They see the proof. They approve. You receive a finished PDF. If you charge for it, your own checkout takes the payment.
Starter ($29/mo) fits most independent shops — 5 templates, 250 renders/mo, hosted fill links. Step up to Pro ($99/mo) when you're ready for storefront embeds, API access, and webhooks into your MIS.
See full pricing · Try the dashboard demo
Weighing other tools? Read StackFill vs PitchPrint and Infigo alternatives, or check a file first with the free PDF preflight checker.
StackFill complements one or replaces a layer of it. If you have a storefront / commerce piece working, a developer can add StackFill to it. If you don't, hosted fill links give you the customer-facing piece without building a storefront.
Most. Standard PDF/X-1a or PDF/X-4 exports from InDesign, Illustrator, QuarkXPress, or Affinity work out of the box. CMYK is preserved through the render path. Send us a sample if you want a sanity check before signing up.
Yes, on Pro and Agency. A developer adds the embed widget to your own site, with your logo and colors, and the customer never leaves you. Hosted fill links live on stackfill.com.
Same engine. Hand it a CSV and you get back one PDF per row, ready to impose. Variable-data is a Pro+ feature.
Upload them once to your team font library; every template binds to the same registry. Fonts never leave your account.