Use the Bitcoin Address Extractor
Paste text into the input area to find Bitcoin address candidates. The extractor looks for Base58 legacy and P2SH candidates, plus Bech32 or Bech32m candidates beginning with bc1, tb1, or bcrt1. It then performs structural and checksum validation and shows each match with its line and context.
How to use the extractor
- Paste text into the input area, or select a file with Upload. The picker accepts
.txt,.csv,.json, and.logfiles. You can also drop a file onto the input area; it is read as text. - Review the results table. Each row shows the address, type label, status, line number, and context snippet; valid type labels include the network where it is recognized.
- Adjust Unique only and Show malformed candidates as needed. The table, output, and counter refresh when either option changes.
Review, filter, and export results
Valid rows use labels such as P2PKH (mainnet), P2SH (testnet), P2WPKH (mainnet), P2WSH (regtest), P2TR / Taproot (mainnet), or Bech32m vN (network). Malformed rows use labels such as Base58 (legacy) or Bech32 and include a failure reason.
- Show malformed candidates controls whether candidates that fail structural or checksum validation remain visible. Turn it off to show only valid rows.
- Unique only removes exact duplicate strings. It preserves case distinctions.
- The counter uses the format
N candidates (X valid, Y malformed)and reflects the active filters. - Copy and Download export the currently displayed address strings. Download creates
bitcoin-addresses.txt. If malformed candidates are displayed, they are included in the export.
What the validation does not check
Matching starts with regular-expression candidate detection, followed by structural and checksum validation. The tool does not query the blockchain or check balances, transactions, activity, ownership, or other external address data. A Valid checksum result means that the string is well-formed according to the checked encoding; it does not confirm that the address exists or is in use. This page targets Bitcoin formats and does not extract other cryptocurrency address formats.
Privacy scope
The extractor script processes pasted or loaded text locally in the browser and contains no request that sends that input to a server. This describes the extraction logic; it is not a page-wide claim about analytics or other services loaded by the site.
Frequently Asked Questions (FAQs)
What Bitcoin address formats does the extractor detect?
The tool detects legacy P2PKH candidates beginning with 1, P2SH candidates beginning with 3, and Bech32 or Bech32m candidates beginning with bc1, tb1, or bcrt1. It checks structure and the relevant checksum.
What does "Malformed" mean?
A malformed candidate matched the general Bitcoin-address pattern but failed one or more structural or checksum checks. This can result from a typo, truncation, or a random string that coincidentally resembles an address. Malformed candidates are flagged with the specific reason they failed, rather than being silently dropped.
Does this tool check balances, transactions, or wallet ownership?
No. It performs structural and checksum validation in the browser. It does not query the blockchain, so it does not check whether an address has been used, holds a balance, or is owned or controlled by anyone.
Why does this tool exist separately from other cryptocurrency address extractors?
Bitcoin uses Base58Check and Bech32/Bech32m formats with Bitcoin-specific version values and human-readable parts. This extractor is limited to those Bitcoin formats and does not target other cryptocurrency networks.
Is my data safe when I paste it here?
The extractor script processes pasted or loaded text locally in the browser and does not contain a request that sends that input to a server. Page-wide analytics or other site services are outside the extractor logic described here.
Does Unique only work across differently formatted duplicates?
Unique only compares extracted address strings as exact matches. It preserves case distinctions, so strings that differ by case are not merged.