Frostblood Review: Fire, Ice, and a Slow-Burn Payoff

The Elemental Enemies-to-Lovers Setup That Almost Gets There

I picked up Frostblood expecting a fun, snowy fantasy romp, and what I got was a book that’s genuinely fun for about 70% of its runtime and then loses the plot right when it should be tightening the screws. It’s not a bad book. It’s a book with a great premise that doesn’t fully trust itself.

Ruby Is a Fireblood in a Frostblood World, and That’s the Whole Hook

Ruby has spent her entire life hiding what she is, because in a kingdom ruled by a Frostblood king who’s made it his personal mission to purge anyone with fire in their blood, being a Fireblood is a death sentence. When her mother is killed and Ruby ends up in the hands of a rebel resistance, she’s handed off to Arcus, a brooding, ice-cold warrior tasked with training her to control her power and, eventually, take down the king. The elemental magic system is the strongest thing here: fire versus ice isn’t just an aesthetic, it’s baked into the politics, the prejudice, and the way these two characters are fundamentally built to be at odds. Ruby herself is prickly and reactive in a way that feels earned rather than written-as-quirky, and I liked that she’s allowed to be genuinely angry for most of the book instead of quippy-angry.

Arcus and Ruby Are Doing Enemies-to-Lovers, But It’s More Slow Burn Than Spark

This is where Frostblood either works for you or it doesn’t. Arcus is the classic ice-cold mentor with a tragic backstory he refuses to talk about, and Ruby is the fire he can’t quite extinguish, thematically and otherwise. The training sequences are honestly some of the best material in the book, full of real tension, competence-porn sparring, and the kind of forced proximity that makes a slow burn actually simmer instead of just sitting there. I wanted more of the two of them figuring out how to trust each other and less of the romance shorthand that kicks in once the plot needs them paired off. It’s not insta-love exactly, but it does compress what should have been a longer emotional arc into a handful of scenes, and I felt the seams.

Where the Book Stalls, and Where It Genuinely Delivers

The middle third sags. Once Ruby leaves the training grounds and the plot has to actually move toward the king, the pacing gets choppy, side characters get introduced and then underused, and a few plot developments feel like they exist to manufacture drama rather than grow out of what’s already been set up. The prose is serviceable but not distinctive, competent YA fantasy voice without a lot of personality of its own. That said, when Frostblood commits to its central relationship and its magic system, it’s genuinely gripping, and the ending picks up real momentum after a slow patch. This is a first book in a trilogy that’s clearly setting up bigger stakes, and you can feel Blake reaching for an Ember in the Ashes or Red Queen style epic without quite having the polish those books have. It’s the kind of book that’s better remembered for its premise and its central pairing than for its plotting, which is a very fixable problem, and one I’m hoping the sequels solve.