iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Public-key encryption lets someone protect information for a recipient without first sharing a secret key with them. The sender encrypts with the recipient’s public key; the recipient decrypts with the matching private key, which must remain secret. The keys are mathematically related, but deriving the private key from the public key is computationally infeasible, according to NIST’s glossary.
What public-key encryption means
Public-key encryption is a way to keep information confidential using two different, mathematically related keys. One key is public and can be shared. The other is private and should be controlled by its owner. To send protected information to someone, a sender uses the recipient’s public key to encrypt it. Only the matching private key is intended to decrypt that ciphertext.
This arrangement addresses a basic problem in secure communication: two people may need to exchange information before they have a safe way to exchange a secret. With public-key encryption, the recipient can publish a public key in advance. Senders can use it without needing to receive the private key or agree on a shared secret first.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteNIST’s CSRC glossary describes public-key cryptography as a family of methods that uses two separate keys for operations such as encryption and decryption, or digital signing and verification. In this article, “public-key encryption” means the confidentiality operation specifically. “Public-key cryptography” is the broader family.
#1 Best Overall
- Ultra-Compact FIDO2 Security Key - Plug-and-stay or carry on a keychain. This USB-A hardware security key offers portable, always-on protection for desktop and mobile use. (Item Size: 0.75 X 0.74 IN x 0.25 IN)
- USB-A Hardware Key for All Devices - Works with USB-A ports on PC, Mac, Android, and other laptop/notebook device. Enables secure, cross-platform login with FIDO2.0 passkey support.
- FIDO Certified Security Key - Meets FIDO and FIDO2 standards. Works with Google, Microsoft, GitHub, Dropbox, and more. Please check service compatibility before purchase.
- Passwordless Login with Passkey - Supports passkey login via WebAuthn and CTAP2. Enjoy password-free sign-ins where supported. Not all websites or services currently support passkeys.
- Advanced Multi-Factor Authentication - Offers 200 FIDO2 passkey slots and 50 OATH-TOTP slots. Strong, flexible 2FA/MFA support across various apps and authentication platforms.
How the public and private keys work together
1. The recipient makes a key pair
A recipient has a public key and a corresponding private key. The public key is meant to be distributed; the private key is not. The keys are mathematical values used by an algorithm, not passwords or ordinary documents. Their relationship lets the public key support encryption while the corresponding private key supports decryption.
2. The sender obtains the recipient’s public key
Before encrypting, the sender needs a public key that actually belongs to the intended recipient. Public availability alone does not establish that association: a key found online could be mislabeled, out of date, or supplied by someone else. The sender’s application therefore needs a trustworthy way to associate the key with the person or service it is meant to reach.
3. The sender encrypts for that recipient
The sender supplies the recipient’s public key and the information to an encryption method. The result is ciphertext: information transformed so it is not readable as the original message without the appropriate decryption operation. A person who has only the public key should not be able to recover the private key in practical terms; NIST characterizes deriving the private key from the public key as computationally infeasible.
4. The recipient decrypts
The recipient uses the matching private key to decrypt the ciphertext. A different recipient’s private key will not be the corresponding key for that encrypted information. If the recipient loses access to the required private key, the public key does not serve as a replacement: it is used to encrypt, not to reverse the operation.
A useful analogy is a publicly available slot that accepts a protected message, paired with a private means of opening it. The analogy captures who can send and who can open, but real systems rely on algorithms, key formats, software, and key-management processes; they are not simply physical locks translated into software.
What public-key encryption does—and does not—establish
Encryption with a recipient’s public key is intended to protect confidentiality against someone who can see the ciphertext but does not possess the matching private key. It does not, by itself, establish who sent the information. Anyone who has the public key can use it to encrypt information for the recipient, so successful decryption alone does not prove the sender’s identity.
Rank #2
- Protect accounts with USB-C & NFC 2FA security key. Hardware-based authentication blocks phishing, credential theft & unauthorized access across cloud, enterprise & personal platforms.
- FIDO2 Level 2 certified Security Key. Works with Apple ID, Microsoft Azure/Entra ID, AWS, Google, Facebook, Salesforce, DUO & more. Compatible with Chrome, Safari & Edge on all major OS.
- Plug & play USB-C Security Key with NFC tap login. No software, drivers or batteries required. Works with Windows PC, MacBook, iPhone, Android & Chromebook for fast, secure authentication.
- Built with FIPS 140-2 Level 3 secure element for advanced encryption. Trusted by IT teams, healthcare, education & government for secure authentication & identity protection.
- IP68 waterproof, dustproof & crush-resistant design. Supports FIDO2, U2F, OTP, PIV, Mini Driver & smart card login. Durable USB security key for long-term enterprise & daily use.
Nor does the public key prove its own owner. A public key can be shared openly, but a user or application needs confidence that it is associated with the intended person or service before relying on it. A certificate can help with that association: NIST defines a public-key certificate as a digitally signed document that binds an identifier to a subscriber’s public key. The certificate is part of the trust process; it is not the private key and does not replace protecting that key.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Public-key infrastructure, or PKI, is the broader set of policies, processes, platforms, and workstations used to administer certificates and key pairs. A certificate may help answer “whose public key is this?” within a system’s trust rules. It does not mean that every certificate is automatically trustworthy in every context; the relevant application must validate it according to its rules.
Public-key encryption and digital signatures are different
Both encryption and digital signatures use public/private key pairs, but they solve different problems and use the keys in different ways. For confidentiality, the sender encrypts using the recipient’s public key and the recipient decrypts using the private key. For a digital signature, the signer uses a private key to create a signature, and another party uses the corresponding public key to verify it.
A signature is not simply a message encrypted “with the private key.” It is a distinct operation, with its own algorithm and purpose. Treating signing as reversed encryption can obscure what each operation proves and can lead to incorrect expectations. A signature-verification result concerns whether the signature matches the signed data and public key under the system’s rules; it is not the same operation as decrypting a confidential message.
The two functions can be used in systems that need both confidentiality and evidence associated with a signer, but one does not automatically provide the other. Encrypting for a recipient does not tell that recipient who sent the ciphertext. Signing something does not, by itself, hide its contents.
How public-key methods differ from symmetric encryption
Symmetric encryption uses a shared secret key: the communicating parties need access to the same secret and must handle its distribution securely. Public-key encryption separates the public encryption key from the private decryption key. That changes the key-distribution problem, but does not eliminate the need to protect secret material or to verify that a public key belongs to the expected recipient.
Rank #3
- Protect accounts with USB-A & NFC 2FA security key. Hardware-based authentication blocks phishing, credential theft & unauthorized access across cloud, enterprise & personal platforms.
- FIDO2 Level 2 certified Security Key. TAA compliant and supports Apple ID, Microsoft Azure/Entra ID, AWS, Google, Facebook, Salesforce, DUO & more. Works with Chrome, Safari & Edge across major OS.
- Plug & play USB-A Security Key with NFC tap login. No software, drivers or batteries required. Works with Windows PC, MacBook, iPhone, Android & Chromebook for fast, secure authentication.
- Built with FIPS 140-2 Level 3 secure element for advanced encryption. Trusted by IT teams, healthcare, education & government for secure authentication and identity protection.
- IP68 waterproof, dustproof & crush-resistant design. Supports FIDO2, U2F, OTP, PIV, Mini Driver & smart card login. Durable USB security key for long-term enterprise and daily use.
| Question | Public-key encryption | Symmetric encryption |
|---|---|---|
| Key arrangement | A related public/private key pair; the recipient’s public key encrypts and the matching private key decrypts. | A shared secret key is used by the parties. |
| Key distribution | The public key may be distributed openly; the private key must stay secret. The public key still needs to be associated with the intended recipient. | The shared secret must be made available securely to the parties who need it. |
| Typical roles | Can support encryption, digital signatures, key transport, and key agreement, depending on the method. | Commonly handles bulk data encryption. |
| Large-message suitability | NIST SP 800-32 describes asymmetric algorithms as relatively slow and poorly suited to directly encrypting large messages. | NIST SP 800-32 identifies symmetric encryption as the practical approach for bulk data in this general division of roles. |
The performance distinction explains why a system may use both kinds of cryptography rather than choosing only one. Public-key mechanisms can help establish or manage key material; symmetric encryption can then protect the larger body of data. NIST SP 800-32 presents this as general explanatory context, not as current advice for selecting a particular algorithm, product, or configuration.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why not encrypt a whole large file directly?
Public-key methods are relatively slow compared with their role in typical bulk-data workflows, and NIST SP 800-32 says they are poorly suited to encrypting large messages directly. A common design approach is therefore hybrid: use a public-key mechanism for a key-management task, then use symmetric encryption to protect the large message or file. The public-key operation helps solve how parties establish or transport key material; it need not transform every byte of the file itself.
The exact design varies by protocol and application. Public-key cryptography may support key transport or key agreement, which are related but distinct ways of handling shared secret material. In key agreement, parties compute shared secret material. These functions should not be casually conflated with encrypting a message: the goal may be to establish material for later symmetric encryption rather than to produce ciphertext by directly applying a public key to the entire payload.
Common misunderstandings to avoid
- “The public key is secret.” It is intended to be shared. The private key is the secret that must be protected.
- “If the key is public, anyone can read what it encrypts.” The public key lets people encrypt for the recipient; decryption requires the matching private key.
- “A public key proves who owns it.” Not by itself. A trustworthy association, often involving certificate and PKI processes, is needed.
- “A digital signature is just encryption in reverse.” Signing and verification are separate operations with different purposes from encryption and decryption.
- “Public-key encryption is the best way to encrypt every byte.” NIST describes asymmetric methods as relatively slow and poorly suited to large messages; systems commonly rely on symmetric encryption for bulk data.
- “Using encryption proves the whole communication is secure.” Encryption addresses confidentiality in the operation described here. It does not, on its own, answer who sent a message or whether the public key was correctly associated with the intended recipient.
What this definition cannot tell you about a specific system
The term describes a cryptographic arrangement, not a guarantee about every implementation. This definition does not identify a particular algorithm, key size, application, certificate policy, or threat model. NIST’s general descriptions explain the roles and limitations of the key types, but the cited NIST SP 800-32 publication is an older explanatory source and should not be treated as current algorithm-selection guidance.
To evaluate a real system, the relevant questions are more specific: which algorithm and protocol does it use, how does it obtain and validate the recipient’s public key, how is the private key stored and controlled, and what happens if that key is lost or compromised? A product or protocol’s use of the phrase “public-key encryption” alone does not answer those implementation questions.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
