Minecraft Title Generator
Build the /title commands for an on-screen title, subtitle, and timing.
What this tool does
Enter a main title, an optional subtitle, choose fade-in, stay, and fade-out timing in seconds, and this tool generates the three separate /title commands Minecraft's on-screen title system actually requires — one setting the timing, one for the subtitle text, and one for the main title text — converting your seconds into the tick-based values the timing command specifically expects.
Why on-screen titles need three separate commands
Minecraft's title display system splits configuration across three distinct commands specifically because each controls a genuinely separate aspect: the times command sets how long the animation takes, while the title and subtitle commands each set their own specific text independently. Running the times command isn't strictly required — Minecraft uses reasonable default timing if you skip it — but setting it explicitly gives you precise control over exactly how the animation feels rather than accepting the default pacing.
Understanding the tick-to-second conversion
Minecraft's internal game clock runs at 20 ticks per second, and the /title times command specifically expects its three timing values in ticks rather than seconds, which is exactly why typing 1 second into this tool's fade-in field produces a value of 20 in the generated command. This tick-based timing system underlies most of Minecraft's internal timing mechanisms, not just titles specifically, and this tool handles the conversion automatically so you never need to do the multiplication by hand.
Choosing effective timing for your title
A fade-in around 0.5 to 1 second feels responsive without being jarringly instant. A stay duration of 2 to 4 seconds gives players enough time to read a typical short title comfortably without lingering so long it starts to feel like it's blocking their view unnecessarily. A fade-out similar to your fade-in, around 0.5 to 1 second, provides a smooth, symmetrical-feeling exit. These aren't rigid rules, just a reasonable, commonly used starting point worth adjusting based on your specific title's length and purpose.
Common uses for on-screen titles
Announcing the start of a minigame round, displaying a player's current objective or quest update, showing a boss's name and health context when a fight begins, welcoming a player who's just joined the server, and marking achievement or milestone moments are all common, practical uses for Minecraft's title display system across servers and custom maps.
Titles versus other Minecraft text display options
Titles differ from ordinary chat messages by displaying prominently across the center of the screen rather than in the scrollable chat log, making them well suited to important, time-sensitive announcements that shouldn't get lost or scrolled past the way a chat message easily can be. Action bar text, a related but distinct display option, shows briefly above the hotbar rather than centered on screen, better suited to smaller, less critical status updates than a full title deserves.
Why subtitle text alone won't display without a title
Minecraft's title system requires the main title text to actually trigger the on-screen display — a subtitle set without ever setting a title won't display on its own, since the subtitle is specifically designed to appear alongside and beneath a main title rather than functioning as a standalone display element. If you only want smaller supplementary text, setting a brief or even empty main title alongside your subtitle is necessary to trigger the display at all.
Using titles in command block sequences and data packs
For repeated or automated title displays — a countdown sequence, a recurring event announcement — the generated commands work well embedded in a command block chain triggered by redstone, or within a data pack function for more sophisticated, version-controlled server logic. Since the commands this tool generates are already correctly formatted, they drop directly into either setup without requiring any additional syntax adjustment.
A note on title text length and screen readability
Very long titles can wrap awkwardly or extend beyond a comfortable reading width depending on a player's specific screen resolution and Minecraft's GUI scale setting, both of which vary considerably between different players' setups. Keeping title text relatively short and punchy — a few words rather than a full sentence — tends to display more reliably and readably across the wide range of screen configurations your players might actually be using.
Combining titles with sound effects for greater impact
Many servers pair a title command with a simultaneous sound effect command specifically to add audible impact alongside the visual display — a triumphant sound for an achievement title, an ominous one for a boss encounter announcement — since the combined audio-visual moment tends to feel considerably more impactful and attention-grabbing than either element alone would on its own.
Testing title timing before deploying it widely
Because title timing is genuinely a matter of feel rather than a single objectively correct answer, testing your generated commands in a private world first, adjusting the fade-in, stay, and fade-out values based on how the animation actually feels in practice, is worth doing before rolling out a specific timing configuration across an entire server or a widely distributed custom map.
Why the target selector matters for title commands specifically
Choosing @a (all players) displays the title to everyone simultaneously, appropriate for server-wide announcements and shared moments. Choosing @p or a specific player's username restricts the display to just that individual, appropriate for personal messages, individual quest updates, or targeted feedback that shouldn't interrupt every other player's screen at the same time. Picking the wrong scope is an easy, common mistake worth double-checking before running a title command on a live server.
A brief history of the title command's role in map-making
Custom adventure and puzzle maps have long used titles as a core storytelling tool, displaying narrative beats, objective updates, and dramatic reveals at key moments throughout a scripted map experience, well before more sophisticated scripting and data pack systems existed to achieve similar effects. Even with today's more advanced options, the humble title command remains one of the most straightforward, reliable ways to deliver a clear, attention-grabbing message at a specific, deliberately chosen moment.
Multi-language and special character considerations
This tool's text escaping handles quotation marks and backslashes correctly in the generated JSON text component, but if you're working with non-English characters or want to mix in color codes or special formatting within your title text, additional JSON text component features beyond plain text — like nested color and formatting objects — may be needed, which is a more advanced use case beyond this tool's focused, straightforward text-input approach.
Why some server plugins offer alternative title systems
Certain server plugin ecosystems, particularly on heavily modified servers, sometimes implement their own custom title or announcement systems layered on top of or instead of vanilla Minecraft's built-in title command, typically offering additional features like richer formatting, scheduling, or conditional triggers vanilla commands alone can't achieve. If your specific server uses one of these plugin systems, its own particular syntax may differ from the vanilla commands this tool generates, worth checking your server's specific documentation.
Using this tool for personal single-player projects
Beyond multiplayer servers, single-player world builders and adventure map creators use titles just as commonly to mark chapter transitions, deliver narrative text, or announce personal milestones and achievements within their own world, using command blocks triggered by redstone circuits, pressure plates, or tripwires to display titles at exactly the right narrative moment as a player explores a custom-built experience.
A closing thought on why good timing elevates a title from functional to polished
The difference between a title that feels abrupt and jarring and one that feels smooth and professionally polished often comes down entirely to timing — the same text with poorly chosen fade and stay values can feel noticeably worse than well-tuned timing applied to that exact same text, which is exactly why this tool makes adjusting and previewing timing values as easy as adjusting the text itself.
Why testing multiple timing presets helps you find the right feel
Rather than settling on the first timing values you try, generating a few different combinations here — a fast, snappy version and a slower, more dramatic version of the same title — and comparing how each actually feels in a live test is a quick, low-effort way to land on genuinely well-tuned timing rather than guessing once and moving on without ever comparing alternatives.
A note on the order commands should run in
Running the times command before the title and subtitle commands ensures the timing configuration is already in place before the actual text displays, avoiding a brief moment where the title might flash using default timing before your custom values take effect. This tool orders its output with exactly this sequence in mind, ready to run top to bottom as generated.
Why an empty subtitle field is handled gracefully
If you leave the subtitle field blank, this tool simply omits the subtitle command entirely from its output rather than generating a command that would display empty, unnecessary subtitle text — keeping the final generated output clean and containing only the commands you actually need for your specific title.
Practical example: a countdown sequence using multiple generated titles
A common technique for minigame start countdowns involves generating several separate title commands — '3', then '2', then '1', then 'GO!' — each triggered in sequence by a timed command block chain with brief delays between them, creating a classic countdown effect entirely from repeated, simple title commands rather than any more complex scripting.
Frequently Asked Questions
Why does this tool generate three separate commands instead of one?
Minecraft's title system splits configuration across three distinct commands because each controls a separate aspect — timing, subtitle text, and main title text — each needing to be set independently rather than combined into a single command.
Why does 1 second become 20 in the generated timing command?
Minecraft's internal game clock runs at 20 ticks per second, and the /title times command expects its values in ticks rather than seconds. This tool handles that conversion automatically.
Do I have to run the times command every time?
No — Minecraft uses reasonable default timing if you skip it. Running it explicitly gives you precise control over exactly how the fade-in, stay, and fade-out feel rather than accepting the default pacing.
What's a good default timing to start with?
Roughly 0.5-1 second fade-in, 2-4 seconds stay, and a similar 0.5-1 second fade-out is a commonly used, reasonable starting point, adjustable based on your specific title's length and purpose.
What are titles commonly used for on servers?
Announcing minigame rounds, displaying quest updates, showing boss names when a fight begins, welcoming new players, and marking achievement or milestone moments are all common practical uses.
How are titles different from regular chat messages or the action bar?
Titles display prominently across the center of the screen, better suited to important announcements than the scrollable chat log. Action bar text shows briefly above the hotbar, suited to smaller status updates rather than a full title.
Will my subtitle show up if I don't also set a title?
No — the subtitle is designed to appear alongside a main title, not as a standalone element. Setting at least a brief or empty main title alongside your subtitle is necessary to trigger the display at all.
Can I use generated title commands in a command block sequence?
Yes — they work well embedded in a command block chain or within a data pack function, since they're already correctly formatted and drop directly into either setup without needing additional syntax adjustment.
Should I keep title text short?
Yes — very long titles can wrap awkwardly or extend beyond a comfortable reading width depending on a player's screen resolution and GUI scale. Short, punchy text displays more reliably across different setups.
Should I use @a or a specific player for my title command?
@a displays to everyone, appropriate for server-wide announcements. @p or a specific username restricts it to one individual, better for personal messages or targeted feedback that shouldn't interrupt every player's screen simultaneously.
Have titles always been used in custom Minecraft maps?
Yes — adventure and puzzle maps have long used titles as a core storytelling tool for narrative beats and objective updates, well before more sophisticated scripting and data pack systems existed to achieve similar effects.
Does this tool support color codes or special formatting within the title text?
It handles plain text with correct quote and backslash escaping. Adding color codes or special formatting requires additional JSON text component features beyond this tool's focused, straightforward text-input approach.
Do server plugins ever replace the vanilla title command?
Sometimes, yes — certain plugin ecosystems implement their own custom announcement systems with richer features. If your server uses one, its syntax may differ from the vanilla commands this tool generates, worth checking your server's documentation.
Does the order I run these three commands in matter?
Yes — running the times command before the title and subtitle commands ensures your custom timing is already in place before the text displays, avoiding a brief flash of default timing. This tool's output is already ordered correctly for this.
What happens if I leave the subtitle field empty?
This tool simply omits the subtitle command entirely from its output, rather than generating a command that would display empty text, keeping the final output clean and containing only what you actually need.
Is this tool useful for setting up a countdown sequence?
Yes — generating several separate title commands ('3', '2', '1', 'GO!') and triggering them in sequence via a timed command block chain is a common, straightforward way to build a countdown effect using nothing but repeated title commands.
Does this tool work the same on Bedrock Edition?
The core title command concept exists on both editions, though exact syntax details can differ slightly. Treat the commands generated here as Java Edition-focused and verify against Bedrock documentation if you're playing that edition specifically.
Can I set fade-in, stay, and fade-out to zero?
Yes — a zero value produces an instant, no-transition effect for that phase, useful for a jarring, abrupt announcement style, though most titles feel smoother with at least a brief fade-in and fade-out rather than an instant snap.
Is there a maximum length for title or subtitle text?
Minecraft imposes a general chat/command character limit that a typical title easily fits within, so length is rarely a practical concern unless you're writing an unusually long subtitle far beyond normal title-length text.
Does this tool cost anything or require an account?
No — completely free with no account or signup required, consistent with every other tool across this site's suite.
Can this tool generate a title with no fade transitions at all, just instant text?
Yes — setting fade-in and fade-out both to zero produces an instant appear/disappear effect with no smooth transition, useful for specific stylistic choices like a jarring alert or warning message.
Will the generated commands work on any Minecraft server type?
Yes — since these are standard vanilla commands, they work on any server running unmodified vanilla command support, including most Spigot, Paper, and Fabric servers that preserve vanilla command compatibility alongside their own plugin systems.