THE FILE FIELD GUIDE

.gpg

OpenPGP Encrypted or Signed Data

Certificates & Keys

GPG is a suffix used for OpenPGP data, including encrypted content, signed data and key material. Establish the actual purpose and encryption method before selecting a workflow; decryption can require a private key or passphrase.

Main use: Handle encrypted or signed data
Data type: Binary data

All sections, questions and sources

Content reviewed：2026-10-19 · Editor：Kai

Opening steps

Choose your environment or purpose to see its steps.

GnuPG / compatible OpenPGP software

Preserve the original and inspect a working copy in a compatible application.

Ask whether it is encrypted content, a signature or key data.
Inspect its type with suitable tools and obtain the required legitimate key.
Review decryption/verification results and specify a separate output destination.

Inspect the received file and its requirements

Establish dependencies and settings before proceeding.

Establish public-key versus symmetric-passphrase encryption.
Check recipient fingerprints and available private keys.
Confirm the expected signer/fingerprint through a separate trusted channel.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

No secret key: compare encryption recipients with available private keys.
Passphrase fails: distinguish private-key unlocking from symmetric encryption.
Public key cannot decrypt: recipient decryption normally needs the private key.
Good signature but unknown identity: verify fingerprint against the intended signer.

GPG → decrypted original content

Decrypt with the correct key/method to an explicitly named output and inspect signature results.
Verify output content, required signature results and storage of decrypted plaintext.

Renaming or ZIP extraction does not decrypt; lost keys/passphrases need not be recoverable.

Separate encryption from signing

Encryption protects confidentiality; signatures verify data against a signing key. Decryption alone does not establish sender identity; inspect signatures and fingerprints.

Source for these steps：GnuPG project · Operational GPG Commands / GnuPG project · OpenPGP Key Management

Worked example: checks before handoff

Example: decrypt a partner’s delivery with the intended recipient key and compare any signature with the partner’s previously confirmed fingerprint.

Source for these steps：GnuPG project · Operational GPG Commands / GnuPG project · OpenPGP Key Management

Related-format differences

Related-format differences
Format / method	Purpose and preserved information
.gpg	Handle encrypted or signed data
ZIP / PEM	ZIP is archiving and PEM belongs to another encoding ecosystem, not equivalent OpenPGP data.
GPG → decrypted original content	Renaming or ZIP extraction does not decrypt; lost keys/passphrases need not be recoverable.

Handling and security

Do not share private keys/passphrases with others or unknown services; decrypted plaintext remains sensitive.

Questions and answers

Can a public key decrypt it?

Recipient encryption needs the matching private key; symmetric encryption needs its passphrase.

Is ASC related?

ASC can represent armored data; identify whether it holds a key, signature or ciphertext.

May decrypted plaintext be published?

Decryption does not change confidentiality/sharing conditions; establish recipient and purpose.

Format facts: name, steward and MIME type

Formal name: OpenPGP Encrypted or Signed Data
Steward / specification: GnuPG project
MIME type: Consult the producer or delivery system. The extension alone does not establish a MIME type.

Primary and official sources

Software documentationOperational GPG Commands
Decryption, signature verification and key operations.
GnuPG project · Link checked：2026-10-16
Software documentationOpenPGP Key Management
Public/private keys, fingerprints and key management.
GnuPG project · Link checked：2026-10-16