How many certificates can I issue at once?

There is no practical limit. Issuance runs from a recipient list, so a cohort of 5,000 costs you the same effort as a cohort of 5. You send the list; every recipient gets their own certificate, their own verification page, and their own email.

What file formats do recipients get?

Every certificate comes out as both a print-ready PDF and a high-resolution PNG, rendered at 2× for retina screens. The PNG is what LinkedIn and X display when a recipient shares their credential. The PDF is what they attach to an application.

Can the certificate carry our own branding?

Yes. We set up your template with your background, logo, colours, fonts, and signature blocks before your first issuance. What goes out is your certificate, not a stock layout with your name dropped into the middle of it.

What happens if I spell a recipient's name wrong?

We regenerate the certificate and the verification URL stays the same, so any link already shared keeps working. This is the practical advantage of a credential that lives at a permanent URL instead of as a PDF sitting in somebody's inbox.

Do recipients need an account to view their certificate?

No. Recipients, and anyone verifying them, reach the credential page directly. No login, no app. Requiring an account to confirm a credential would defeat the point of issuing a verifiable one.

Certificate generator

A digital certificate generator that produces credentials people can verify

Most certificate tools are design tools. They produce a good-looking file, and the moment it leaves your hands nobody can tell whether it is genuine. Certifications.ng generates certificates that carry proof of who issued them: cryptographically signed, QR-verifiable, and hosted at a permanent link.

Request a Demo See how verification works

The difference between a certificate and a verifiable credential

A certificate made in a design tool is a picture of a claim. Anyone with the same template and an hour can produce one that looks identical, and the only way to check it is to email the issuing organisation and hope somebody answers. That is not a criticism of design tools, which are the right answer when nobody has to check anything; choosing a certificate platform sets out when they are, and when they stop being.

A verifiable credential carries its own evidence. The recipient's name, the award, your organisation, and the issue date are signed with a private key that only your organisation holds. Anyone can check that signature against your public key, and if a single character of the credential is altered, the check fails. No phone call, and nothing to take on trust.

Worth a footnote on the term itself: "digital certificate" also names an unrelated piece of internet infrastructure, which is why searching for it returns two different subjects.

How issuing works

Nobody on your side has to learn a tool to issue, manage templates, or handle key material — and if you would rather not, you never have to. Send the list and we run the batch. That matters most for organisations issuing in two or three large cohorts a year, where software would be forgotten between one and the next. Issuing more often than that, you can sign in and issue under an approved award yourself, as many times as you like. What stays ours either way: setting the award up in the first place, and sending the recipient mailing.

Step 1 The recipient list arrives: Each recipient's name and email, plus the award and the date. Send us the spreadsheet, or sign in and paste the list yourself under an award we have already set up. That is the whole input either way.
Step 2 We generate the batch: Every recipient gets a certificate rendered from your template, signed with your organisation's private key, and given its own permanent verification URL.
Step 3 Recipients are notified: Each person receives a branded email with a link to their credential, which they can download, share, or add straight to their LinkedIn profile.

What every generated certificate carries

A cryptographic signature: Each certificate's details are signed with your organisation's Ed25519 private key at the moment of issuance. Change any field afterwards and the signature stops matching.
A scannable QR code: Printed on the certificate itself, so anyone holding a paper copy can scan it and land on the live verification page. Paper is where forged certificates usually survive, because paper is where nobody thinks to check.
A permanent verification page: A public URL showing who was awarded what, by whom, and when, with the signature checked in the visitor's own browser.
PDF and PNG files: Print-ready and share-ready, generated at 2× resolution and hosted for you, so a lost download is never a support ticket.

The signing mechanism, key custody, and what tamper-evidence does and does not prove are described in full on the security page.

Certificates and badges, one at a time or a cohort at a time

The design was never the work. The work is the hundred rows of a spreadsheet, the mail merge, the export, the bounced emails, and the six months of "can you resend mine?" that follow. Issuing 800 certificates should not cost 800 times what issuing one costs. Bulk issuing covers what a batch does, what the ceiling is, and what stands between a recipient list and several hundred signed URLs.

Badges work the same way. If you want a shareable badge image rather than a formal certificate layout, the award is set up as a badge and issuance is otherwise identical, with the same signature and the same verification page behind it.

Frequently asked questions

How many certificates can I issue at once?: There is no practical limit. Issuance runs from a recipient list, so a cohort of 5,000 costs you the same effort as a cohort of 5. You send the list; every recipient gets their own certificate, their own verification page, and their own email.
What file formats do recipients get?: Every certificate comes out as both a print-ready PDF and a high-resolution PNG, rendered at 2× for retina screens. The PNG is what LinkedIn and X display when a recipient shares their credential. The PDF is what they attach to an application.
Can the certificate carry our own branding?: Yes. We set up your template with your background, logo, colours, fonts, and signature blocks before your first issuance. What goes out is your certificate, not a stock layout with your name dropped into the middle of it.
What happens if I spell a recipient's name wrong?: We regenerate the certificate and the verification URL stays the same, so any link already shared keeps working. This is the practical advantage of a credential that lives at a permanent URL instead of as a PDF sitting in somebody's inbox.
Do recipients need an account to view their certificate?: No. Recipients, and anyone verifying them, reach the credential page directly. No login, no app. Requiring an account to confirm a credential would defeat the point of issuing a verifiable one.

See it with your own certificate

We will set up your template, issue a sample batch, and show you exactly what your recipients and their employers will see.

Request a Demo