**Export Public Key**

This command will export an ascii armored version of the public key:

`gpg --ouput public.pgp --armor --export user@email`

**Export Secret Key**

This command will export an ascii armored version of the secret key:

`gpg --output private.pgp --armor --export-secret-key user@email`

---

**Security Concerns, Backup, and Storage**

A PGP public key contains information about one's email address. This is generally acceptable since the public key is used to encrypt email to your address. However, in some cases, this is undesirable.

For most use cases, **the secret key** need not be exported and **should not distributed**. If the purpose is to create a backup key, you should use the backup option:

`gpg --output backupkeys.pgp --armor --export --export-options export-backup user@email`

This will export all necessary information to restore the secrets keys including the trust database information. Make sure you store any backup secret keys off the computing platform and in a secure physical location.

If this key is important to you, I recommend printing out the key on paper using [paperkey](https://www.jabberwocky.com/software/paperkey/). And placing the paper key in a fireproof/waterproof safe.

**Public Key Servers**

In general, it's not advisable to post personal public keys to key servers. There is no method of removing a key once it's posted and there is no method of ensuring that the key on the server was placed there by the supposed owner of the key.

It is much better to place your public key on a website that you own or control. Some people recommend [keybase.io](https://keybase.io/) for distribution. However, that method tracks participation in various social and technical communities which may not be desirable for some use cases.

For the technically adept, I personally recommend trying out the [webkey](https://www.gnupg.org/blog/20160830-web-key-service.html) domain level key discovery service.