# Importing versus sweeping Bitcoin private keys Importing a Bitcoin private key teaches a wallet about existing spending authority without moving the funds. Sweeping constructs a transaction that spends available funds controlled by that key to another wallet’s destination, paying a network fee. The distinction matters for backups: an imported key may not be recoverable from the new wallet’s seed, while a completed sweep can move funds under its normal derived keys. Evidence: [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html); [Transactions](https://developer.bitcoin.org/devguide/transactions.html); [Hierarchical Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki) Canonical: https://degreesofsatoshi.com/encyclopedia/bitcoin-import-vs-sweep/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:29:20.637Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Import:** No on-chain move merely from loading a key ([Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html)) - **Sweep:** A real transaction with a fee ([Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html)) - **Backup:** Imported keys can require separate backup ([Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html); [Securing your wallet](https://bitcoin.org/en/secure-your-wallet)) ## Copying a key does not revoke other copies If two applications hold the same private key, both can attempt spends from the same outputs. Importing does not make the first copy invalid. A successful sweep instead consumes selected outputs and creates new ones under the destination’s conditions. Only import or sweep keys you are authorized to use. A displayed public address is insufficient: it can create a watching-only view without any signing capability. Evidence: [Transactions](https://developer.bitcoin.org/devguide/transactions.html); [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html) ## Account for the destination and fee For an illustrative 200,000-satoshi old-key balance with a 2,000-satoshi sweep fee, the new output receives 198,000 satoshis. The wallet must discover and be able to spend the relevant outputs, and the transaction must still confirm. The old destination can receive new funds later. A sweep is not a forwarding rule, so update future payment instructions rather than assuming every later receipt will automatically reach the new wallet. Evidence: [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html); [Transactions](https://developer.bitcoin.org/devguide/transactions.html) ## Match recovery material to the resulting wallet Electrum’s documentation distinguishes its seed-derived wallet from a wallet made by importing private keys. It warns that imported-key wallets require their own backup. Other products can organize imports differently, so use their actual backup specification. After a sweep, verify the recipient output and preserve the destination wallet’s complete recovery arrangement. Do not destroy old recovery material while relevant funds or unresolved transactions remain. Evidence: [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html); [Hierarchical Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki) ## Questions ### Does importing a private key cost a Bitcoin fee? Loading a key alone does not publish a transaction. Spending from it later does. Sweeping, by contrast, explicitly creates a transaction moving funds to another destination and has transaction-fee considerations. Evidence: [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html); [Transactions](https://developer.bitcoin.org/devguide/transactions.html) ### Will my existing seed back up an imported private key? Not necessarily. A seed restores keys derived from it; an independently imported key is outside that derivation. Electrum explicitly documents a separate imported-key wallet backup requirement. Evidence: [Hierarchical Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki); [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html) ## Claims and scope ### bitcoin-import-vs-sweep-quick-answer Importing a Bitcoin private key teaches a wallet about existing spending authority without moving the funds. Sweeping constructs a transaction that spends available funds controlled by that key to another wallet’s destination, paying a network fee. The distinction matters for backups: an imported key may not be recoverable from the new wallet’s seed, while a completed sweep can move funds under its normal derived keys. Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02. Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-import-vs-sweep-fact-import Import: No on-chain move merely from loading a key Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-import-vs-sweep-fact-sweep Sweep: A real transaction with a fee Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-import-vs-sweep-fact-backup Backup: Imported keys can require separate backup Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html) — Electrum. Electrum-specific sweep/import distinctions, seed recovery scope and address discovery. Locator: Does Electrum trust servers?; Can I import private keys from other Bitcoin clients?; Can I sweep private keys from other Bitcoin clients?; What is the gap limit?; How do I upgrade Electrum?. Retrieved: 2026-10-02T18:53:56.378Z. - [Transactions](https://developer.bitcoin.org/devguide/transactions.html) — Bitcoin developer documentation. Inputs, outputs, authorization, change, coinbase exceptions and fee accounting. Locator: Introduction; Spending An Output; P2PKH Script Validation; Multisig; Transaction Fees And Change; Avoiding Key Reuse. Retrieved: 2026-10-02T18:53:53.759Z. - [Hierarchical Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki) — Bitcoin Improvement Proposals. Deterministic key derivation, backup scope and public/private child derivation. Locator: Motivation; Extended keys; Security. Retrieved: 2026-10-02T18:53:54.013Z. - [Securing your wallet](https://bitcoin.org/en/secure-your-wallet) — Bitcoin.org. Backup scope, online exposure, offline signing, custody and software update practices. Locator: Be careful with online services; Backup your wallet; Encrypt your wallet; Offline wallet for savings; Hardware wallets; Keep your software up to date. Retrieved: 2026-10-02T18:53:53.659Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees of Satoshi editorial project. “Importing versus sweeping Bitcoin private keys.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-import-vs-sweep/