Hash rate units: converting MH/s to GH/s to match a pool's dashboard
I was comparing my own rig's hash rate, reported in MH/s by its mining software, against a pool's dashboard that displayed everything in GH/s — the numbers looked wildly different in magnitude until I converted them.
We write the way we argue on the bench: exact factor, one sharp trap, one worked example you can re-check.
I was comparing my own rig's hash rate, reported in MH/s by its mining software, against a pool's dashboard that displayed everything in GH/s — the numbers looked wildly different in magnitude until I converted them.
Start with the exact relationship. Everything else is just arithmetic and knowing when to round.
The factor that settles arguments
This is the relationship our converters use. Screenshot it if you have to — just stop re-deriving it from a half-remembered blog post.
1 GH/s = 1,000 MH/s
Write that line once at the top of your notes. Every later arithmetic step should point back to it instead of inventing a friendlier number mid-stream.
The mistake that keeps showing up
Comparing a hash rate in MH/s directly against one in GH/s without converting, since the same physical performance can look either tiny or huge depending purely on which unit prefix is used.
I still write the unit next to every intermediate value. It looks pedantic until it catches the one swap that would have shipped wrong.
- Write down the known value in GH/s.
- Confirm the target unit is really MH/s, not a similar-looking one.
- Apply the factor: 1 GH/s = 1,000 MH/s.
- Round only at the end, to the precision your tool or spec supports.
Worked example
A mining pool's dashboard reports the pool's total hash rate in GH/s, and your own rig's software shows MH/s.
2.5 GH/s × 1000 = 2500 MH/s
That's 2500 MH/s — round only to the precision your tool or spec actually needs.
Flip the factor once as a sanity check. If you do not land near the starting number, you mixed definitions or inverted the direction.
Quick reference table
| GH/s | Calculation | MH/s |
|---|---|---|
| 1 | 1 × 1000 | 1000 |
| 2 | 2 × 1000 | 2000 |
| 5 | 5 × 1000 | 5000 |
| 10 | 10 × 1000 | 10000 |
Use the table for speed once you trust the factor. Do not use it as a substitute for understanding which definition of the unit you are on.
Why the exact number matters
Misjudging your rig's relative contribution to a pool (or a scam pool's inflated claims) starts with comparing hash rate numbers on the same scale.
Precision is not about showing off decimals. It is about making sure the shopping list, the machine setting, and the acceptance check are all describing the same physical quantity.
Pocket recap
Multiply GH/s by 1,000 to get MH/s — 2.5 GH/s is 2,500 MH/s, the number to compare directly against your own rig's software readout.
Keep the converter link nearby for the next time the same debate shows up in a group chat. Re-typing the factor from memory is how the wrong cousin of a unit sneaks back in.
Try the converters mentioned in this article
FAQ
What is the exact GH/s to MH/s factor here?+
1 GH/s = 1,000 MH/s
Should I round partway through the calculation?+
No — carry full precision through the multiplication and round only the final answer, to the precision your tool, gauge, or spec actually supports.
What's the single biggest mistake people make with this conversion?+
Comparing a hash rate in MH/s directly against one in GH/s without converting, since the same physical performance can look either tiny or huge depending purely on which unit prefix is used.
This article was written by The Turbo Unit Converter engineering desk (Applied units & field metrology) and last reviewed on 2026-07-26 against NIST SP 811 and the BIPM SI Brochure. Read our full editorial policy.