How do I overclock a Raspberry Pi for XMR mining?

You can overclock a Raspberry Pi for XMR mining by improving its cooling, raising its CPU clock in small steps, and testing each change under a real mining load. Expect a modest experiment, not reliable profit: Monero’s RandomX mining algorithm favors CPUs with much more cache than a Pi has, and overclocking cannot fix that limitation.

Check your Pi before changing anything

Your exact Pi model matters. Do not copy clock or voltage settings from a guide written for another model.

• Use a 64-bit operating system. Check that your mining software supports your Pi’s ARM processor architecture.
• Check your memory. RandomX’s faster operating mode needs a 2,080 MB dataset, plus memory for the miner and operating system. A 4 GB or larger Pi gives you more breathing room.
• Know the cache limit. Cache is small, fast memory near the processor. RandomX benefits from about 2 MB of L3 cache per mining thread, or worker. Pi processors do not provide the large L3 cache that makes desktop CPUs competitive.
• Back up your microSD card. An unstable overclock can crash your Pi and corrupt stored data.

RandomX also has a slower light mode with a 256 MB cache, but its lower memory requirement does not make a small Pi competitive.

Fix cooling and power first

Fit a heatsink and active fan, or a good actively cooled case. Mining keeps the processor busy continuously, unlike short everyday tasks.

Use a reliable power supply rated for your model. Disconnect unnecessary USB devices if power is marginal.

Before overclocking, run your miner at its normal speed. Record its hash rate—the number of mining calculations it performs each second—and check:

vcgencmd measure_temp
vcgencmd get_throttled

Throttling means the Pi slows itself down because of heat or power limits. A get_throttled result of 0x0 means no current or recorded warning flags since boot. Other values need decoding; they can include past events, not just current problems.

Raise the CPU clock gradually

On current Raspberry Pi OS releases, boot settings are usually in /boot/firmware/config.txt. Older releases commonly use /boot/config.txt.

Back up the file, then open it:

sudo cp /boot/firmware/config.txt /boot/firmware/config.txt.bak
sudo nano /boot/firmware/config.txt

For example, on a Pi 4 normally running at 1,500 MHz, a small first step could be:

[pi4]
arm_freq=1600

This is an example, not a universal setting. Some Pi 4 boards already run faster by default, and Pi 5 needs different targets.

Change only the CPU frequency initially. Leave GPU clocks alone. Avoid force_turbo=1 and copied voltage settings. Voltage controls differ between models; raising voltage increases heat and can shorten hardware life.

Save, reboot, and test before making another small increase.

Test mining performance, not just booting

A Pi that starts successfully may still fail after sustained mining.

Run the same miner settings for at least an hour after each change, then test promising settings for longer. Watch for:

• Freezes, restarts, or miner errors.
• Heat or undervoltage warnings.
• Lower sustained hash rate despite a higher clock.
• Increased electricity use without a worthwhile speed gain.

Try fewer mining threads too. More workers can compete for limited memory resources. If unstable, lower the clock; if the Pi will not boot, restore the configuration using another computer.

The bottom line

For your Pi, cooling and stability matter more than a headline clock speed. Keep only an overclock that improves sustained mining performance, and use measured power consumption with a live XMR mining calculator before assuming it earns money.