What Sparrow is
Sparrow is a free, open source desktop Bitcoin wallet for macOS, Windows and Linux. Most wallets hide how a payment is built. Sparrow shows it: every coin going in, every output coming out, the fee, and the change. It can hold keys itself, drive a hardware signer, coordinate a , or simply watch a wallet whose keys live somewhere else.
It is the wallet I use most often. It suits you once words like , recovery phrase and address type are familiar. If they are not yet, start with BlueWallet and come back.
Version 2.5.6, released on 29 October 2026, was current when I checked. Everything below was compared with that release, and the button and menu names come from Sparrow's own source code.
Sparrow: features ↗ · Sparrow 2.5.6 release ↗
Download and verify
- Download the installer for your system from sparrowwallet.com/download, along with the manifest and signature files listed beside it.
- Verify the download before you open it. The download page gives the steps for each operating system. If you already run a Sparrow you trust, it can check a new download for you under Tools > Verify Download.
- Install and open it. The first run shows a short welcome sequence that ends with two buttons: Configure Server and Later or Offline Mode.
Verification is what protects you from a tampered installer, so do not skip it. Verifying downloads explains what the signature and the checksum each prove.
Choose how Sparrow connects
A wallet has to ask something for your balances and hand something your payments. Sparrow gives three choices under File > Settings... > Server, and the choice decides who learns which addresses are yours.
Using a public server means it can see your transactions.
- Public Server. Fastest to set up and the least private. The operator can see every address you ask about and the internet address you ask from. Fine for learning and small amounts.
- Bitcoin Core. Sparrow connects directly to your own node, version 24 or later. Nobody else sees your queries. A wallet with a long history takes longer to load this way, and looking up some older transaction details needs the node's transaction index switched on.
- Private Electrum. You run an Electrum server such as Electrs or Fulcrum next to your node and point Sparrow at it. Loading is quick, and you can reach it from another computer over Tor. Most node packages offer one as an add-on.
Press Test Connection before you close the window. The switch at the bottom right of the main window then shows which kind of server you are on: yellow for public, green for Bitcoin Core, blue for private Electrum.
If you enter an .onion address, Sparrow starts its own Tor connection. If you set a proxy instead, Sparrow sends its outside connections through it and still reaches addresses on your home network directly. When a Tor proxy is in use, Sparrow also sends your transactions out through other sources over Tor. Without one, the server you are connected to broadcasts them. Running a node covers the node side.
Sparrow: connect to Bitcoin Core ↗ · Sparrow: FAQ ↗
Create a wallet
Decide the wallet's job first. A wallet whose keys sit on this computer is convenient and only as safe as the computer. A wallet built from a hardware signer keeps the keys off the computer. A watch-only wallet can see and prepare, and cannot sign.
Enter a name for this wallet:
☐ Has existing transactions
Two settings come before the key.
Policy Type has three options: Single Signature HD for an ordinary one-key wallet, Multi Signature HD for multisig, and Single Signature SP for a wallet that receives Silent Payments.
Script Type sets the kind of address the wallet uses.
| Script Type | Addresses start | When to choose it |
|---|---|---|
| Native Segwit (P2WPKH) | bc1q | The usual choice. Low fees and supported almost everywhere. |
| Taproot (P2TR) | bc1p | The newest type. Check that your signer and the people paying you support it. |
| Nested Segwit (P2SH-P2WPKH) | 3 | Only if a service cannot pay a bc1 address. |
| Legacy (P2PKH) | 1 | Only to recover or match a very old wallet. Highest fees. |
Three things about the software wallet steps are easy to get wrong:
- Write the words on paper. No photo, no notes app, no cloud. Sparrow makes you type them back before it creates the key.
- A passphrase makes a different wallet. If you tick Use passphrase?, Sparrow does not store the passphrase. A wrong one opens a different, empty wallet with no error. Back it up separately from the words.
- The wallet password is not the passphrase. The password only locks the wallet file on this computer. It does not replace your written backup.
The same pane also restores an existing wallet. Sparrow can import a Shamir backup (SLIP39, since version 2.0.0) and a Codex32 backup (since 2.4.0).
Sparrow: quick start ↗ · Sparrow source: wallet settings ↗
Use a hardware signer, or just watch
The other three Keystores buttons keep the keys off the computer.
- Connected Hardware Wallet. Plug the device in by USB and press Scan.... Sparrow lists what it finds and imports the public key for the script type you chose. Since version 2.4.0, Discover can look across the device's accounts for a wallet that already has history.
- Airgapped Hardware Wallet. For a signer that never plugs in. Export the wallet's public details from the device as a QR code or a file, then pick your device in Sparrow and scan or load it.
- Watch Only Wallet. Paste a public key or an output descriptor. You can see balances, make receive addresses and prepare payments. Signing has to happen somewhere else.
Import the public export from your signer, never its recovery words. Then check a receive address on the signer's own screen before you send anything to the wallet (see Receive below).
Sparrow's features page lists the signers it works with, and the list changes. Recent versions added more and raised the firmware some devices need. Check your exact model there before you buy around this guide.
A public key or descriptor cannot spend, but it does reveal your whole history. Keep it as private as you would a bank statement.
Receive
- Open the Receive tab. It shows the next address, a QR code and a Label: field.
- Type a label that says where the coins come from, such as "Bisq trade, 14 Feb". You will need it later when you choose what to spend.
- With a hardware signer, press Display Address and compare the address on the device with the one on screen. Sparrow shows addresses in blocks of four characters to make that easier.
- Share the address or the QR code. Get Next Address moves on to a fresh one.
Send
- Open the Send tab. Fill in Pay to: with the address, Label: with a note for yourself (Sparrow requires one), and Amount:. Max sends everything.
- Set the fee. The Fee panel has three views, Target Blocks, Mempool Size and Recent Blocks. All three help you pick a rate in sats per virtual byte. A higher rate confirms sooner.
- Choose Optimize: Efficiency for the cheapest payment or Privacy to let Sparrow shape the payment so it gives less away.
- Look at the diagram under the form. Coins you are spending are on the left. The payment, the change coming back to you and the fee are on the right.
- Press Create Transaction.
As well as a plain address, Pay to: accepts a PayNym, a Silent Payment address and a BIP 353 name that looks like an email address.
Choose which coins to spend
Your balance is a set of separate coins, each with its own history. Spending two together tells anyone watching that one person owned both. Coin control means choosing them yourself. Bitcoin privacy explains why that matters.
The UTXOs table has five columns: Date, Output, Address, Label and Value. Right-click a coin and choose Freeze UTXO to stop Sparrow picking it automatically. Frozen coins fade in the list. Unfreeze UTXO puts it back. Freezing is useful for coins you want to keep apart and for tiny coins that cost more to spend than they are worth.
Review, sign and broadcast
Creating a transaction does not send anything. Sparrow opens it in its own tab so you can check it first: the diagram, each input and output, and the raw data below.
- Check the destination, the amount, the fee and the change.
- Press Finalize Transaction for Signing.
- Sign. A software wallet or a USB signer uses Sign. For a signer that never plugs in, use Show QR and then Scan QR, or Save Transaction and Load Transaction to carry a file across on a memory card.
- On a hardware signer, read the address and amount on the device before you approve. The device's screen is the one to trust.
- Press Broadcast Transaction.
The unsigned payment that travels between Sparrow and the signer is called a PSBT, a partially signed Bitcoin transaction. It is a standard format, which is why signers from different makers work with Sparrow. To open one that somebody else prepared, use File > Open Transaction and pick File..., From Text... or From QR....
When a payment is stuck
A payment waits when its fee rate is lower than what miners are currently taking. Right-click the unconfirmed transaction in the Transactions tab.
- Increase Fee (RBF) replaces a payment you sent with the same payment at a higher fee. Sparrow marks its payments as replaceable by default.
- Cancel Transaction (RBF) replaces it with one that sends the coins back to you.
- Increase Effective Fee (CPFP) is for a payment someone sent you. It spends the incoming coin with a fee high enough to pull both through.
Transaction troubleshooting covers how to tell a slow payment from a failed one.
Multisig
A multisig wallet needs several keys to spend, for example any two of three. Losing one key does not lose the coins, and stealing one key does not take them. Multisig explains the idea and whether you need it.
- File > New Wallet, then set Policy Type to Multi Signature HD.
- Set Cosigners to the total number of keys and M of N to how many must sign. Two of three shows as "2 / 3".
- Choose the Script Type. Use Native Segwit (P2WSH) unless you have a reason not to. Sparrow does not offer Taproot for multisig.
- Fill each keystore tab (Keystore 1, Keystore 2 and so on) from a different signer, using the same four buttons as before.
- Press Apply.
- Save the wallet's descriptor straight away: File > Export Wallet... and choose Output Descriptor.
The descriptor is the map of the wallet: every public key, the threshold and the address type. Recovery words alone do not rebuild a multisig. Keep a copy of the descriptor with each key's backup. Backing up a multisig goes through it.
Spending works as above, repeated: each signer adds a signature to the same PSBT, by USB, QR code or file, until enough have signed and Broadcast Transaction becomes available.
PayNyms and Silent Payments
Both give you one code you can publish that still produces a fresh address for every payment.
- PayNyms. Tools > Show PayNym opens your payment code and your contacts. Paying a PayNym for the first time needs a one-off notification transaction on the blockchain. PayNyms has the detail.
- Silent Payments. No notification transaction. Sparrow has been able to send to an address starting sp1 since version 2.3.0, and to sign those payments on a hardware signer since 2.4.0. Version 2.5.0 added wallets that receive them, using the Single Signature SP policy type. Silent Payments explains how they work.
Back up, and recover
| What | Why | Where to get it |
|---|---|---|
| Recovery words | They are the key. | Written down when you created the wallet. |
| Passphrase | Without it the words open a different wallet. | Only if you set one. Store it apart from the words. |
| Output descriptor | Needed to rebuild a multisig. Handy for any wallet. | File > Export Wallet... > Output Descriptor |
| Labels | Your record of where each coin came from. | File > Export Wallet... > Labels |
To recover in Sparrow, create a new wallet, choose New or Imported Software Wallet, pick the word count and type your words in, with the passphrase if you used one.
You are not tied to Sparrow. The descriptor is a standard that Bitcoin Core reads too, so a wallet made here can be rebuilt there. Labels export in the BIP 329 format, which other wallets can import.
Practise on test coins before you rely on any of this. Tools > Restart In switches Sparrow to Testnet or Signet, where coins have no value. A recovery rehearsal shows what to practise.
What has changed
- Whirlpool is gone. Sparrow removed its coinjoin client in version 1.9.0 in April 2024. A tutorial that shows a mixing tab is describing an old version.
- Update if you use Sparrow's built-in Tor. Version 2.5.6 bundles a newer Tor, which the release notes say the Tor network now requires. Older versions may fail to connect.
- Recent releases tighten security. Versions 2.5.4 to 2.5.6 add more checking of what a server tells Sparrow. That is a good reason to stay current, and to verify each download.
Before you rely on it
- You verified the download.
- You know which server Sparrow is using, and who runs it.
- Your words are on paper, and the passphrase is stored separately if you set one.
- You checked a receive address on your signer's screen.
- Every coin has a label.
- For multisig, the descriptor is saved with each key's backup.
- You have restored the wallet once, on test coins or a spare device, before trusting it with savings.
If you would like to set this up with someone alongside you, connecting Sparrow to a node, building a multisig or practising coin control are all things I cover in mentorship sessions.
Sources & further reading
Researched 15 November 2026. Software and services change: check the current documents before you act.
- Sparrow: download and verification ↗
- Sparrow: features ↗
- Sparrow: quick start ↗
- Sparrow: FAQ ↗
- Sparrow: connect to Bitcoin Core ↗
- Sparrow: releases and release notes ↗
- Sparrow 2.5.6 release ↗
- Sparrow 1.9.0 release (Whirlpool removed) ↗
- Sparrow source code: interface files ↗
- Sparrow: security policy ↗
- BIP 174: partially signed Bitcoin transactions ↗
- BIP 329: wallet labels export format ↗
BlueWallet: a clearer everyday wallet → · Your balance is a collection of stories → · Multisig → · Verify the software before you trust it → · Running a node →
This guide replaces an earlier walkthrough on this site. Read the original walkthrough.
