Here is how to judge and adjust them.

Where the numbers come from

A skin draws hit circle numbers from ten files: default-0.png through default-9.png (plus @2x versions for high resolution). Two lines in the [Fonts] section of skin.ini control them:

• HitCirclePrefix – the file name prefix, default unless the author moved the numbers into a subfolder or renamed them
• HitCircleOverlap – how many pixels neighbouring digits overlap when the number has two digits (10, 11, 12…)

If a skin looks fine on single-digit combos but the "10" or "12" looks squeezed or spread apart, HitCircleOverlap is usually the line to change, not the images.

The score and combo counters are separate fonts (ScorePrefix and ComboPrefix), so you can change circle numbers without touching the HUD.

What makes numbers readable

Good circle numbers have three things in common:

1. Contrast against every combo colour. The digit sits on top of your hit circle tinted by the combo colours. White numbers with a thin dark outline survive almost any colour; plain white on a pale yellow combo colour disappears.
2. A size that leaves a ring of circle visible. If the digit fills the whole circle, you lose the edge you aim at – especially with high circle size (CS) maps where circles are already small.
3. Simple shapes. Decorative fonts look nice in a screenshot, but at speed a stylised 1 and 7, or a 6 and 8, are easy to mix up. Plain sans-serif digits are safer.

Do you need numbers at all?

Some experienced players make every default-x file transparent and play with no numbers. It removes clutter and they read order from the pattern instead. That works if you mostly play maps with predictable flow, but it hurts on overlapping stacks, back-and-forth patterns and anything with tricky slider order – exactly the moments when numbers help most.

A softer option: keep the numbers, but make them smaller and slightly transparent, so they are there when you need them and quiet otherwise.

A quick test you can run

Pick one map with a long combo (so you reach two-digit numbers) and one map with stacked notes. Play both at your usual speed and watch a replay. Check:

• Can you read 10–19 without the two digits blurring together?
• Is every number visible on every combo colour in the skin?
• On stacks, can you tell which circle is on top just from the number?

If one of those fails, swap in a different number set rather than changing the whole skin.

Borrowing numbers from another skin

Number sets are one of the easiest parts to transplant. Copy the ten default-x files (and their @2x versions) from a skin you like into a copy of your current skin, then copy its HitCirclePrefix and HitCircleOverlap values too – the overlap was tuned for those exact images.

To find a set worth borrowing, I look through skin previews on osuskins.org, which lists osu! skins with gameplay screenshots, so you can see how the digits sit inside the circles before you download anything.

Summary

• Numbers come from default-0 to default-9; prefix and overlap live in skin.ini [Fonts]
• Outline or shadow for contrast on all combo colours
• Leave a visible ring of circle around the digit
• Plain digit shapes beat decorative ones at speed
• Test two-digit combos and stacks before you commit

It is a ten-file change, and it is often the difference between a skin you like looking at and a skin you can actually read.