[6] Keybase supports publicly connecting Twitter, GitHub, Reddit, and Hacker News identities, including websites and domains under one's control, to encryption keys.

[14] Keybase allows users to prove a link between certain online identities (such as a Twitter or Reddit account) and their encryption keys.

Instead of using a system such as OAuth, identities are proven by posting a signed statement as the account a user wishes to prove ownership of.

In addition to the web interface, Keybase offers a client application for Windows,[15][16] Mac,[15][16] Android,[17][16] iOS,[16] and most desktop Linux distributions,[16] written in Go with an Electron front end.

Each device is also given a per-device NaCl (pronounced "salt") key to perform cryptographic operations.

[3] If the recipient (the online alias owner) has an account on Keybase, they will seamlessly receive the message.

If the recipient doesn't have a Keybase account, and later signs up and proves the link between the online account and their devices, the sender's device will rekey the message for the recipient based on the public proof they posted, allowing them to read the message.

Single user folders are displayed at keybase.pub and are also accessible by opening the directory in the mounted version of the filesystem.

[6] Only users who are marked as writers can edit its contents, however, any readers can access the files stored there.

"[25] Each team has a private folder in the Keybase filesystem, and a number of chat channels (similar to Slack).