A LitRPG status screen works when it earns its place on the page, which means it shows a number that just changed, points at something the reader has been waiting for, and then gets out of the way. Treat it as an interface you are designing rather than a database you are dumping, because the difference between a screen a reader lingers over and one they scroll past is almost entirely in what you choose to leave out.
What a LitRPG status screen is actually for
A status screen is the persistent character-sheet display a LitRPG uses to show the reader the state of the protagonist's build: levels, attributes, skills, classes, and whatever resource the story runs on, rendered as an in-world game interface rather than described in prose. It is the single most recognizable convention of the genre, and it is also the one that new writers most often get wrong, because it looks like the easiest thing in the world to write and is in fact a small exercise in interface design. When I read submissions and early chapters from authors moving into web fiction, the status screen is usually where I can tell in about thirty seconds whether someone has thought about the reader or is just transcribing a spreadsheet, and the tell is almost always length: the writers who understand it show me four lines, the ones who do not show me forty.
The reason the screen matters at all is that numeric progression is the promise of the genre, and the screen is where that promise gets paid off visibly. In a series like Matt Dinniman's Dungeon Crawler Carl, the System interface is not decoration; it is the mechanism by which the reader feels Carl claw upward against a set of rules that are actively trying to kill him, and the screens are doled out so that each one confirms a change we have been sweating over for a chapter. Compare that to a book where the author reprints the full sheet after every skirmish, and the two feel completely different even when the underlying math is identical. If you want the wider context on how progression choices ripple through everything else in a serial, I wrote a broader piece on how to write web fiction that this sits underneath, but the status screen deserves its own treatment because it is where so much goodwill is quietly won or lost.
Show the delta, not the database
The single most useful habit you can build is to show only what changed, because a status screen is interesting in proportion to how much of it is news. A reader does not need to re-read that the protagonist still has 12 Strength; they need to see that Strength just went from 12 to 15, and they want the three points to mean something they can feel in the next fight. My feeling about this is that the full sheet is a reference document and the reader almost never actually needs the reference; what they need is the diff, the one or two lines that moved, framed so the movement carries weight. When Shirtaloon's He Who Fights with Monsters surfaces an ability or an affliction, it tends to isolate the thing that is new rather than dumping the character's entire loadout, and that restraint is a large part of why the screens stay readable across a very long series.
This is also the cleanest way to keep a status screen from turning into what readers in the genre call yard trash, the endless low-value clutter that trains an audience to scroll. There is a real debate about whether stat displays help or hurt a book at all, and I unpack the case on both sides in a companion piece on when stat blocks work and when they don't; the short version I will stand behind here is that the ones that work are ruthless about omission. If a stat has not changed and is not about to be tested, it does not belong on the screen. Defiance of the Fall, which runs some of the densest sheets in the genre, gets away with it precisely because the density is reserved for the moments where a build genuinely reconfigures; the everyday chapters do not carry that weight, and neither should yours.
Format it so it survives a phone screen
Design the screen to read in a single narrow column, because the overwhelming majority of web fiction is consumed on a phone, and anything wider than roughly forty characters wraps into a ragged mess the moment it hits a real reader. This is the most common purely mechanical mistake I see, and it is invisible on the laptop where the author writes and brutal on the device where the reader reads. A status screen that leans on wide multi-column alignment, name on the left, value tabbed far to the right, looks crisp in your editor and then collapses into broken lines on an iPhone, and a broken interface reads as amateur no matter how good the prose around it is. Keep it vertical, keep the label-and-value pairs on their own short lines, and resist the urge to draw elaborate ASCII borders that only hold their shape at desktop width.
Practically, that means building the screen inside a formatted block that preserves its structure rather than typing it as loose paragraph text, and then previewing it at phone width before you ever publish. This is one place the tool you write in genuinely matters: in the IlorisNovel editor, which you can open with no account, you can drop a status screen into a formatted block and see immediately how it reflows, and I would rather an author catch a wrapping problem in thirty seconds in the editor than discover it in the comments after a chapter goes live. Whatever you write in, the discipline is the same. Treat the phone as the primary screen, treat the desktop as the exception, and let that constraint keep your screens short, because a display that has to survive a narrow column is a display you will naturally trim.
Give the interface a voice
The status screen is a character, so decide early whether the System that produces it is neutral, bureaucratic, hostile, or something stranger, and then be consistent. This is the move that separates a memorable LitRPG interface from a generic one, and Dungeon Crawler Carl is the obvious teacher here: the System's snide, over-caffeinated tone turns what could be dry notifications into some of the funniest and most menacing beats in the series, and readers quote those screens the way they quote dialogue. Alexander Wales does something quieter but just as deliberate in Worth the Candle, where the game interface is uncanny in a way that keeps raising the question of what the interface actually is, and that unease is doing real thematic work rather than just reporting numbers.
You do not have to be funny or uncanny; you have to be intentional. A System that describes a new skill in cold, clipped, faintly patronizing language tells the reader something about the world the protagonist is trapped in, and a System that is warm and encouraging tells them the opposite. My advice, then, is to write two or three sample screens early and read them aloud, because the voice of the interface is easy to drift on across a long serial and very noticeable when it slips. The screen is one of the few places in your book where the world speaks directly to the reader in its own register, and that is too good an opportunity to waste on flavorless boilerplate.
Surface it only when it carries weight, and know when to cut it
Space your full status screens out so each one lands as an event, and lean on partial displays or a single changed line for everything in between. A new class, a tier threshold, the close of a major arc, those are the moments that can carry a whole sheet, and if you reserve the full screen for them, readers will actually stop and read it rather than skimming past a form they have learned to ignore. The rhythm matters more than the frequency; a screen that arrives exactly when the reader is hungry to see the payoff of a hard-won fight is worth ten that arrive on schedule whether anything happened or not, which is the same retention logic that governs how you end a chapter across any web serial.
And it is worth saying plainly that plenty of superb progression fiction uses no status screen at all. Will Wight's Cradle runs on a clear, escalating cultivation ladder with no game interface anywhere in sight, and it is one of the best-selling progression series ever written; the reader always knows exactly where Lindon stands, and Wight conveys it entirely through prose and reaction. I think the lesson there is that the status screen is a tool for making trackable numbers legible, not a badge you have to wear to belong to the genre, so if your story's progression is not actually built on stats a reader needs to see, a screen will only get in the way. Use one because the numbers are load-bearing and the reader will genuinely enjoy watching them move, and when neither is true, trust your prose to carry it and let the screen go.
Common questions about writing a LitRPG status screen
What is a status screen in LitRPG?
A status screen is the persistent character-sheet display a LitRPG uses to show the reader the state of the protagonist's build: levels, attributes, skills, classes, and whatever resource the story runs on, rendered as an in-world game interface instead of described in prose. It is the standing snapshot of who the character is right now, distinct from a system message, which is a one-off notification that fires when something changes. Think of the status screen as the dashboard and the system message as the alert.
How often should a status screen appear in a LitRPG?
Less often than most first drafts assume. A good rule of thumb is to surface the full status screen only at genuine milestones, a new class, a tier threshold, the end of a major arc, and to use short partial displays or a single changed line the rest of the time. Readers do not need the whole sheet after every fight; they need the one number that moved. Spacing the full screens out keeps each one feeling like an event rather than a form the reader learns to scroll past.
How do you format a status screen so it reads on mobile?
Keep it narrow, keep it short, and never rely on wide multi-column alignment, because most web fiction is read on a phone where anything past roughly forty characters wraps into a mess. Favor a single vertical column of label-and-value lines, cut any row that has not changed and does not matter to the scene, and preview it at phone width before you publish. A status screen that looks tidy on a laptop and collapses into ragged wrapping on a phone is worse than a sentence of prose.
Should every LitRPG have a status screen?
No, and treating it as mandatory is how you end up with screens that add nothing. The status screen is a tool for making numeric progression legible and satisfying, so it earns its place only when the numbers themselves are load-bearing to the story. Plenty of celebrated progression fiction, Will Wight's Cradle among the clearest examples, runs with no status screen at all and loses nothing. Use one because your story's progression is built on trackable stats, not because the genre expects it.
What is the difference between a status screen and a system message?
A status screen is the standing snapshot of the character's full build, while a system message is a single transient notification that fires the moment something changes, a level gained, a skill unlocked, a quest completed. The status screen answers where do I stand; the system message announces something just happened. Most LitRPGs use both, and the common mistake is letting the message stream get so noisy that readers start skipping it, which then makes the occasional full status screen land harder by contrast.
by Jacob Tam · July 27, 2026
I run IlorisNovel, a platform for web fiction writers. If this kind of craft writing is your thing, the rest of the blog lives here.