How to speed up initial Monero blockchain sync

Overview

The fastest safe way to complete an initial Monero sync is to remove the common bottlenecks: slow storage, inefficient settings for your hardware, and insufficient free disk space. The Monero daemon (monerod) must download and validate the blockchain. Validation is not optional if you want the security guarantees of running your own node.

Older advice often suggested downloading a “raw blockchain” file (blockchain.raw) and importing it. Today, the Monero documentation notes that raw import typically does not speed things up versus normal peer-to-peer sync, because disk I/O and verification tend to dominate performance. The import tool (monero-blockchain-import) is mainly useful if you exported your own bootstrap file earlier (for example, moving a verified chain between disks or machines).

Important safety note: the official Monero guide on importing the blockchain warns against “dangerous unverified import” for any file downloaded from the internet. Only consider unverified import if you exported the file yourself and you are sure it was already fully verified. See: Importing the Monero Blockchain from an outside source.

If your immediate goal is simply to use a wallet before your own node finishes syncing, consider using a Monero wallet with a remote node temporarily (trade-off: you trust that remote node with some metadata). For command-line wallet creation, see How to create a Monero command line wallet. If you need to restore an existing wallet, see How to restore a Monero wallet from your 25 word seed.

Do this First

Below is a practical “do this first” procedure that keeps the original spirit of this page (get synced faster), but updates the steps to match current tooling and current best practices.

1. Use fast storage (the biggest real-world win). Put the blockchain data directory on an SSD or NVMe drive. Initial sync on HDD is commonly much slower due to random reads/writes.
2. Ensure you have enough free disk space, or prune. Pruning reduces storage needs significantly with no privacy or security downside for normal use. See Moneropedia: Pruning.
3. Linux/macOS: download Monero binaries from official sources and verify them. The most reliable starting point is the official downloads page: getmonero.org downloads. Verification guidance: Verify Monero binaries signature.
4. Linux/macOS: start monerod in pruned mode (recommended default for most users).
   cd ~ # Start a pruned node (saves disk space; typically helps machines with limited storage) ./monerod --prune-blockchain --sync-pruned-blocks

   Why this helps: less data is stored and managed locally, which can reduce disk pressure during sync. Trade-off: you still validate blocks; pruning mainly reduces storage footprint.

5. Optional (advanced): choose a faster db sync mode on reliable systems.

   Monero supports tuning database sync behavior. The safest default is the default configuration; faster modes can improve performance but may increase corruption risk if the system crashes or loses power. Reference flags are documented in the monerod reference.

   # Example: faster database sync behavior (advanced) # Use only if you understand the trade-offs and have stable power/storage. ./monerod --prune-blockchain --sync-pruned-blocks --db-sync-mode fast

   If you are unsure, do not set --db-sync-mode manually and keep the defaults.

6. Optional (legacy/rare): importing a bootstrap file you exported yourself.

   Only do this if blockchain.raw is from your own earlier export, or from a source you can independently verify. The import tool is documented here: monero-blockchain-import reference.

   # Import a local bootstrap file into your data directory (verification ON by default) ./monero-blockchain-import --input-file /path/to/blockchain.raw

   Common misunderstanding: importing a downloaded blockchain.raw is not a “safe shortcut.” If you skip verification, you are explicitly trusting the file instead of validating consensus rules yourself.

7. Windows: download official binaries and run a pruned node.

   Use the official downloads page: getmonero.org downloads. Verify before extracting when possible: Verify Monero binaries signature.

   REM In Command Prompt, change directory to where monerod.exe is located cd C:\path\to\monero REM Start a pruned node monerod.exe --prune-blockchain --sync-pruned-blocks
8. After your node is synced, create or open your wallet.

   For CLI wallet creation, see How to create a Monero command line wallet. For sending/receiving using the CLI, see How to send and receive Monero (command line).

   When your wallet displays a seed phrase, write it down offline and keep it safe. Never store it in email or cloud notes.

What to expect (signs it’s working)

• monerod steadily increases its synchronized height and continues downloading blocks.
• Eventually you will see output indicating you are synchronized with the network (wording may vary by version).
• CPU usage during initial sync is normal; disk activity is usually the limiting factor on slower drives.

Common problems (and fixes)

• Sync is extremely slow on HDD. Move the data directory to an SSD/NVMe and restart. If you must stay on HDD, expect significantly slower sync.
• Disk full / low space errors. Use pruning (--prune-blockchain) or free space. Pruning guidance: Moneropedia: Pruning.
• Corruption after an unexpected power loss. Avoid aggressive sync settings on unstable power, and prefer the defaults. Faster modes can improve speed but may increase recovery headaches after crashes.