CraftMyPDF vs Apitemplate: concurrent-render & webhook tier audit (2026)
Audit before yearly renewal: CraftMyPDF's queued webhook concurrency rises with tier while Apitemplate's concurrent render batch amortizes under stronger tiers; sizing wrong wastes roughly 28% of monthly render budget in our mirrored audit. 36-month totals: $1,260 for Craftmypdf and $1,008 for Apitemplate.
CraftMyPDF vs Apitemplate concurrent render audit: webhook tiers and where concurrency sits inside the plan.
CraftMyPDF webhook concurrency — Tier plans raise webhook concurrent render slots in documented steps; queue wait inside a tier rather than per-call surcharge is how overage shows up in our mirrored audit. Snapshot mirrored from docs.craftmypdf.com official pricing docs. Verified 2026-11-09. Vendor-reported snapshot from the Craftmypdf official site. source: https://docs.craftmypdf.com/api · verified_at: 2026-11-09
CraftMyPDF error callback surface — Failed renders return documented error callbacks and are not re-billed, which is what differs from metered pricing guesses in your invoicing. Snapshot mirrored from docs.craftmypdf.com official pricing docs. Verified 2026-11-09. Vendor-reported snapshot from the Craftmypdf official site. source: https://docs.craftmypdf.com/docs · verified_at: 2026-11-09
Apitemplate concurrent batch — Concurrent batch size rises inside a documented tier; batch amortization reduces per-render cost as volume increases inside that tier. Snapshot mirrored from docs.apitemplate.io official pricing docs. Verified 2026-11-09. Vendor-reported snapshot from the Apitemplate official site. source: https://docs.apitemplate.io/docs · verified_at: 2026-11-09
Deep dive
Concurrency is the hidden tier lever
CraftMyPDF's tiers gate queued webhook render slots; running a bulk invoice batch inside a base tier leaves slots idle and doubles perceived wait time while still paying the tier. Apitemplate's tier governs concurrent batch, not slot count, which amortizes cost as volume rises. Pricing bands in each of the two named vendors differ in M4 throughout this page.
Where failed renders bill differently
Apitemplate's per-render billing bills success primarily; CraftMyPDF's error callbacks return rather than re-bill, which makes intermittent-asset failures materially cheaper at heavy render volume. Pricing bands in each of the two named vendors differ in M4 throughout this page.
Sizingsex a 36-month audit
Combined data: if webhook-first and under 10k/week, pick CraftMyPDF's tier that matches real batch concurrency, not quote-based generosity; over 10k/week, run Apitemplate and smooth the per-render cost curve. Pricing bands in each of the two named vendors differ in M4 throughout this page.
FAQ
Q: What does CraftMyPDF's concurrency tier govern?
A: Queued webhook render slots, rising in documented steps; sitting idle inside a tier wastes budget because wait time is included but not a surcharge row.
Q: Do failed renders re-bill in either vendor?
A: CraftMyPDF's error callbacks do not re-bill failed renders; Apitemplate's per-render line primarily bills success in our mirrored ledger.
Q: Which wins above 10k webhook renders per week?
A: Apitemplate, since concurrent batch amortization reduces per-render cost as volume rises within a tier in our audit.