Fantasy gives you a blank universe and a dangerous amount of freedom. The writers who finish a fantasy novel are rarely the ones with the most elaborate world — they are the ones who built just enough world to tell a story, then told it. This guide walks through how to write a fantasy novel: choosing your corner of the genre, building a world and a magic system that hold together, and getting the book structured, drafted, and read.
Know your subgenre before you start
"Fantasy" is a dozen different promises to a reader. Epic fantasy promises scope and a world at stake; grimdark promises moral murk and cost; romantasy promises a central relationship with real heat; cozy fantasy promises warmth and low stakes; progression fantasy promises a power curve you can feel. Each comes with reader expectations about length, pacing, and tone.
Pick your subgenre early, because it sets your defaults. A romantasy that buries its central couple under 200 pages of politics has broken its promise; an epic that resolves the dark lord in chapter four has broken a different one. Read widely in your lane first — you are learning the genre's grammar, not to copy it but to know which rules you are choosing to keep or break.
Start with the story, not the world
Worldbuilding is the most fun part of fantasy and the most common place to drown. It is entirely possible to spend eight months drawing maps and naming dynasties without writing a single scene. Avoid that by building the world around a story rather than the other way round.
Start from the story you want to tell — a character, a conflict, a question — and build only the world that story touches. You need the city your hero flees, not the trade routes of a continent they never visit. The rest can wait until a scene demands it.
This is the iceberg rule: most of your world will never appear on the page, and that is correct. You build depth so the visible part feels real, the way a good actor knows a character's backstory the audience never hears. Aim to know more than you show, and show only what the scene needs.
Build a magic system with rules and a cost
Magic is the genre's signature, and the fastest way to lose a reader is magic that can do anything. If there is always a spell to solve the problem, there is no tension left to solve.
The fix is limits. Decide what magic cannot do, what it costs, and who pays. Magic that drains the caster, demands a rare material, or exacts a moral price creates stakes; magic with no cost creates a vending machine. The single most important rule of thumb: if magic costs the hero something in chapter three, it cannot conveniently solve everything in chapter twenty. Internal consistency is what makes the impossible feel real.
Magic systems sit on a spectrum from hard to soft. A hard system has explicit rules the reader understands and can predict — useful when magic solves problems, because the reader needs to know the limits to feel the tension. A soft system stays mysterious and atmospheric — useful when magic creates problems and wonder rather than resolving them. Neither is better; pick the one that fits your tone, and introduce at least a hint of it in the first act so a later use never feels like a cheat.
Keep the world consistent
A fantasy reader will forgive an invented continent but never a contradiction. The currency, the distances, who can do magic and at what price, who is dead — break any of these and the spell collapses. Across a single novel that is hard enough; across a series it is where most fantasy authors come undone.
Keep a single source of truth — a story bible — for names, rules, relationships, timelines, and the magic's limits, and check the draft against it rather than your memory. This is exactly what a world bible is for, and it is one of the things Novelmint keeps for you automatically: a living record of characters, places, and rules that holds continuity across chapters and across books, so the magic that cost a hand in book one still costs a hand in book three.
Structure the plot for scope
Fantasy plots are big — multiple point-of-view characters, parallel threads, a world-level stakes line braided with personal ones. That scope is the appeal and the trap: it is easy to lose the spine under the sprawl.
A reliable frame is the three-act structure scaled up: a setup that establishes the world and the want, a long middle of rising complications and reversals, and a climax that pays off the stakes you planted. Map the big turns as beats before you draft, and lay the point-of-view threads side by side so you can see the pacing — whose chapter comes when, and whether a thread has gone quiet for too long. Working in beats on a visual Timeline makes a multi-POV epic legible in a way a linear document never will; you can reorder a reveal or rebalance a neglected thread before a word of prose is committed.
Reveal lore without the info-dump
You have built a deep world. The temptation is to show it all, and that temptation produces the three classic fantasy openings that kill momentum: the prologue history lecture, the "as you know" conversation where characters explain things they both already know, and the rulebook chapter that spends five thousand words on magic mechanics before anyone casts a spell.
Resist all three. Give the reader exactly what they need to follow the current scene, and no more. Reveal a prophecy one cryptic line at a time; surface a political rivalry inside a tense council scene; teach the magic through a character using it and getting it wrong. Lore lands when it is doing a job in a scene, not when it is delivered in a lump. When a draft does swell with exposition, an editorial pass that strips padding and "telling" is how you find the lump and cut it — the same pass that removes the filter words and tics that read as AI.
Draft it, finish it, get it read
A finished, flawed fantasy novel beats a perfect world bible with no book attached. Build enough world to start, draft the story to the end, then revise for consistency and pace. The worldbuilding you skipped will mostly turn out to be worldbuilding you never needed.
And a fantasy novel is meant to be read, not filed. When the draft holds, publish it where fantasy readers actually gather — release it chapter by chapter, let readers in, and build the audience as the story unfolds. That is the whole arc Novelmint is built for: structure the world, draft it in your voice, keep the continuity, and put the finished chapters in front of readers who pay to keep turning the page.