Challenger 8

What Reviewers Say

Reviewers generally agree that the Hoka Challenger 8 represents a significant update, moving the series forward with increased cushioning, a redesigned outsole, and a more accommodating fit. It maintains its reputation as a versatile “door-to-trail” option, offering a plush, comfortable, and stable ride across roads, gravel, and non-technical trails. While some note the continued use of CMEVA foam and a slight weight increase, the overall consensus is that the Challenger 8 is a robust, dependable, and durable everyday running shoe, particularly beneficial for heel strikers and those seeking a roomier toe box. Its versatility makes it suitable for a wide audience.

Strengths

• Excellent and increased cushioning

• Flexible for a max-stack trail shoe

• Roomier toe box and accommodating fit

• Impressive durability and minimal wear over hundreds of miles

• Fantastic airflow, breathability, and quick drying

• Better suited for heel strikers with great stability

• Redesigned lugs provide excellent grip on mixed terrain, including sloped snow and loose rock

• Secure midfoot fit and lockdown

• Comfortable yet responsive midsole

• Good stack to weight ratio

• Highly versatile for roads, gravel, and non-technical trails

Drawbacks

• Outdated CMEVA foam

• Slightly heavier than the previous version (v7)

• Price increase

• Non-gusseted tongue

• Limited performance on steep, technical terrain

• Lacks high-end responsiveness for speed workouts

Who It's For

The Hoka Challenger 8 is ideal for runners seeking a single, versatile shoe for both road and non-technical trail running, including gravel. It particularly benefits heel strikers and individuals who prefer a roomier toe box. Reviewers suggest it's an excellent everyday running shoe for those who mix up their mileage and running surfaces, and its adaptability also makes it a good choice for traveling. It's recommended for most runners, for most distances, and on most running surfaces, especially where extreme technical terrain is not encountered.