SyeQ: Quick Clarification on MarkupGo Credits Before Purchase
Hi there,
I’m very interested in MarkupGo for automating PDF and image generation, but the credit system is unclear. Could you clarify:
1. Does 1 credit = 1 PDF or 1 image? Or does it vary by file size/complexity?
2. Are there different credit costs for dynamic templates vs. simple conversions?
3. Do API calls (e.g., image transformations, previews) consume credits? If so, how many per action?
4. Is there a way to preview credit usage before generating files?
A clear breakdown would help me decide—your tool looks perfect for my workflow, but I want to avoid surprises. Thanks!
Thanks.
Sye
togedir
Dec 29, 2025A: Hi Sye,
Happy to clarify — here’s a simple breakdown of how credits work in MarkupGo:
1. Credit usage
• 1 PDF = 3 credits
• 1 image = 1 credit
This does not vary by file size, page count, or complexity.
2. Templates vs. simple conversions
There’s no difference in credit cost. Dynamic templates and simple conversions cost the same.
3. API calls & previews
Only the final render consumes credits.
• Image transformations work only on images generated by MarkupGo
• Other API calls (previews, configs, etc.) do not consume credits
• External images or PDFs are not eligible for transformations
4. Previewing credit usage
There’s no separate preview for credit usage, but it’s straightforward:
• Generating a PDF → 3 credits
• Generating an image → 1 credit
No hidden rules or surprises beyond that 🙂
Hope this helps, and feel free to reach out if you have more questions!