Why our PDF API uses two engines
A single-engine PDF API forces a trade-off between speed and capability. Splitting the engine into a Go-native fast path and a Chromium fallback removes the trade-off for the most common shapes. Here is how we route, what we measured, and what we got wrong.
By LightningPDF Jun 4, 2026 5 min read