ASC SIG
File conversion

Convert ASC to SIG

QUICK ANSWER
Is it possible to convert ASC to SIG?
Yes - ASC converts to SIG.

Run gpg --dearmor < file.asc > file.sig in a terminal to produce the binary .sig directly. The resulting file verifies a target file exactly the same way the .asc does.

On this page

Tested on macOS, Windows & Linux
Last verified Oct 2026

More free converters

HEIC, PNG, WEBP, MP3 and more - every tool here is free.

Open the toolbox

Why convert ASC to SIG?

An .asc detached signature and a .sig detached signature carry identical OpenPGP cryptographic data - the only difference is encoding. Some verification scripts or tools, including certain Linux kernel release workflows, expect the binary .sig form and refuse ASCII-armored .asc input.

How to convert ASC to SIG

GnuPG FREE

Run gpg --dearmor < file.asc > file.sig in a terminal; GnuPG strips the Base64 armor and writes the raw binary OpenPGP signature to file.sig.

Gpg4win FREE

Install Gpg4win, open Command Prompt or PowerShell, and run gpg --dearmor file.asc; rename the output file.asc.gpg to file.sig.

About these formats

Quality & what to watch

  • Both .asc and .sig contain the same OpenPGP signature packet; gpg --verify produces the same result with either.
  • Not every .sig is an OpenPGP signature - confirm the .asc starts with -----BEGIN PGP SIGNATURE----- before converting; a public key or message block would produce a meaningless .sig.
  • Running gpg --dearmor file.asc outputs file.asc.gpg, not file.sig; use the pipe form for a clean filename.

Frequently asked questions

Does converting `.asc` to `.sig` affect whether the signature verifies?
No - the cryptographic content is identical; gpg --verify file.sig release-file and gpg --verify file.asc release-file produce the same result.
Do I still need the original public key after converting?
Yes - converting between .asc and .sig does not affect the key requirement; you still need the signer's public key imported into your keyring.
Can I go back from `.sig` to `.asc`?
Yes - run gpg --armor < file.sig > file.asc to re-add the ASCII armor.