The fundamental difference
Both approaches solve the same problem, but with opposite philosophies:
- S/MIME builds on certificates from official CAs — like HTTPS. You buy a certificate, and an authority vouches for your identity.
- PGP relies on a web of trust — users sign each other's keys; trust emerges from the network, not from a central authority.
Side-by-side
| S/MIME | PGP / OpenPGP | |
|---|---|---|
| Trust | Certificate Authority (CA) | Web of Trust |
| Key distribution | Automatic (signature contains cert) | Manual or keyserver |
| Client support | Outlook, Apple Mail, Thunderbird natively | Thunderbird natively; Outlook/Apple Mail via plug-in |
| Mobile | iOS / Android natively | Additional apps required |
| Central management | Very good (certificate rollout via MDM) | Cumbersome |
| Key recovery | Possible (CA / escrow) | Difficult to impossible |
| Cost | Certificate (~40–200 EUR / user / year) | Free |
| Use | Enterprises, public agencies | Tech-savvy community, IT security |
When S/MIME is the better choice
- Enterprises with centralised IT / MDM.
- Communication with public agencies (many use S/MIME).
- Users who do not want to install additional software.
- Compliance requirements that mandate a trust anchor.
When PGP is the better choice
- Individuals and small teams who do not want to trust a commercial CA.
- Communication with journalists, activists, the open-source community.
- Technically experienced users who manage keys themselves.
What neither delivers
Neither S/MIME nor PGP prevents phishing or protects metadata. The subject line, sender and recipient remain visible. Only content and attachments are encrypted. To protect against forged senders you need DMARC.
Can they run in parallel?
Technically yes — a mail client can support both approaches. In practice this is rarely sensible: users often do not know which approach they are currently using, and key management doubles. It is better to roll out a single solution consistently.