FAQs
Answers to the common questions.
The questions we hear most often, with straight answers. If something isn't covered here, write to us and we'll add it.
What is Certfill?
Certfill is a certificate issuance and verification platform for institutions. You upload your design, map your recipient data, and Certfill generates each certificate, delivers it by email, and stores a tamper-proof verification record for every credential issued.
Can I try Certfill before paying?
Yes. The Free plan lets you issue up to 25 certificates per month, indefinitely, with no time limit and no credit card. It's the most reliable way to test the workflow against your real data before committing to volume. See the pricing page for the full breakdown.
How does pricing work?
Certfill is priced per certificate issued. There are no monthly fees and no platform subscriptions on the Free, Standard, or Premium plans. You pay only for the certificates you actually send. Drafts, previews, and unsent certificates are not billable.
Can I use my own certificate design?
Yes. Certfill accepts image files (PNG or JPG) on the Standard plan and above. The Free plan uses templates from the Certfill library. Custom designs work with the same field-mapping engine, so personalisation is identical regardless of source.
How long does setup take?
1 to 5 minutes for most institutions. Upload your design, map the fields onto the template, write the email message, import a CSV, and you're ready to issue. The platform handles generation and delivery from there, regardless of recipient count.
How does the verification link work?
Every certificate carries a unique, permanent URL. When a verifier visits it, they see the recipient's name, programme, certificate ID, issue date, and an instant tamper-proof confirmation that the credential was issued by your institution. No login, no friction. Identifiers are cryptographically random and stored append-only, so a link that wasn't issued by Certfill simply won't resolve.
Where is my data stored, and is it used for AI training?
Data lives on a single, well-known cloud provider with a documented compliance posture. Each customer's data is logically isolated; we don't run shared compute across customer datasets. Encryption is TLS 1.2+ in transit and AES-256 at rest. Recipient data, certificate content, and your design files are never used to train models or build comparative datasets. Full architecture summary on the Security page.
Still have a question?
If your question isn't here, the team is one email away. We respond within one business day, usually sooner.