Roblox publishes previous usernames. It does not publish previous display names. Those two sentences are the whole answer, and most tools promising "full Roblox name history" are quietly relying on you not knowing the difference.
No. Roblox exposes a username history endpoint but has no equivalent for display names. A past display name is only recoverable if somebody recorded it while it was live. Going forward, a monitor can catch each change as it happens.
People arrive at this question from two directions. Either they remember a name on a profile that no longer shows it, or they want to know when they last changed their own. The first is usually not answerable. The second sometimes is, but not through the route most people try.
Two names, two very different histories
A Roblox account carries three identifiers. The numeric user ID never changes. The username is the one in the profile URL, unique across the platform, and it costs Robux to change. The display name is the friendly label shown above it, it does not have to be unique, and changing it is free.
Roblox's public Users API includes an endpoint that returns previous usernames for a given user ID. You can see the same data on a profile page by opening the past-names list. It is not always complete, and names removed for policy reasons will not appear, but it exists and it is public.
There is no matching endpoint for display names. The Users API reference lists routes to set a display name and to validate one, and nothing that returns earlier values. Roblox stores the current display name and serves that.
| Field | Cost to change | Past values public? |
|---|---|---|
| User ID | Cannot change | Not applicable |
| Username | Robux | Yes, via username history |
| Display name | Free | No |
The free part matters more than it looks. Because a display name change costs nothing, people change them often, sometimes weekly. That produces exactly the situation this question comes from: a name you clearly remember, attached to an account you can still find, with no way to show the name was ever there.
Why the asymmetry is not an oversight
Usernames are addresses. The profile URL contains one, groups reference one, and old links break when they change. Keeping a public record of previous usernames lets people follow an account across a rename, which is why the endpoint exists at all.
Display names are labels. They were introduced so a person could present a name to other players without exposing the unique handle attached to their account. Publishing a permanent archive of every label someone ever chose would undo a good part of that. Roblox's display name documentation describes the field as changeable and does not describe a public history.
So the gap is a design decision, not a missing feature waiting to be added. Any tool claiming to reveal past display names is either showing you username history under the wrong heading, or showing you records it collected itself.
Check the history that does exist first
Before assuming the answer is no, confirm which name you are chasing. Open the profile and look at the two lines at the top. The larger one is the display name. The one beginning with an @ is the username. If the name you remember was the @ handle, you are in luck.
Take the numeric user ID from the profile URL and check the username history for it. Our guide to checking Roblox username history walks through that, and username versus display name versus user ID covers the distinction in more detail if the profile layout is confusing you.
If the name you remember was the friendly label, no public lookup will return it. Nothing you do to the user ID changes that.
Starting a record from today
The only reliable way to have display name history tomorrow is to be recording it now. That is an unsatisfying answer to someone asking about last month, and it is still the accurate one.
RoTrail reads the profiles on your watchlist on a schedule, keeps the last successful values, and reports a display-name event when the new value differs from the saved one. The record starts at your first successful check. It contains nothing from before that.
Practically, that means adding an account before you need the history, not after. If you run a group and want to know when a moderator changes their presentation, add them now. If you are keeping track of your own changes, add your own account and let the first check settle.
Keep the list short. Two profiles you actually read beat twenty that produce noise you scroll past. The player tracker setup guide covers the watch controls and the first-check behaviour.
What a change event proves about timing
A recorded event carries the time the difference was observed, which is not the time the edit was made. If checks run hourly and someone renames at 14:05, the event lands at the next successful check. The gap is the interval, plus any delay from Chrome sleeping or a request failing.
This matters if you are trying to establish a sequence. "The display name changed at some point between 14:00 and 15:00" is a defensible statement. "The display name changed at 15:00" is not, and the difference will matter to anyone reading your notes carefully.
A change that reverts inside one interval is invisible. Someone can rename, be seen by other players, and rename back, and a scheduled monitor reports nothing at all. Chrome's alarms reference explains why the schedule is approximate rather than exact, and why alerts arrive late covers the practical causes.
Reading the tools that say otherwise
Search results for this question include sites offering a display-name history lookup. Check what they actually return before trusting the label. Most return the username history endpoint, which is public and free, under a heading that mentions display names.
A few collect their own observations, the same way RoTrail does. That can be genuinely useful, and it comes with the same limit: their record starts when they started looking, and it covers accounts they happened to be watching. It is a sample, not an archive.
What should stop you outright is any site asking for a Roblox password, a session cookie, or a two-step code in exchange for name history. Reading a public profile needs none of those. Roblox's account safety guidance is worth a minute if you are unsure what a legitimate tool needs, and our extension safety checklist lists the permissions worth questioning.
Checking your own display name changes
For your own account you have one route nobody else does: your email and your Robux transaction records. A username change is a purchase and leaves a record. A display name change is free and leaves no receipt, so that route helps with one field and not the other.
If you have changed your display name recently and want to know when, check your own screenshots, your messages, and anywhere your name appears next to a timestamp. A friend's group chat is often a better record than any lookup tool.
Questions about Roblox display name history
Does the username history list include display names?
No. It returns previous usernames only. If a result shows names you never used as your @ handle, treat the source as unreliable.
Can I see when someone last changed their display name?
Only if you or a tool you use had recorded an earlier value. The profile as it stands today carries no edit date.
Does changing a display name break my profile link?
No. The URL uses the numeric user ID, and that never changes. A username change alters the vanity path but the ID link keeps working, which is why searching by ID is the reliable habit.
How often can someone change a display name?
Roblox limits how frequently the change can be made rather than charging for it. Because there is no public history, the count is not something an outside observer can verify.
Will RoTrail show me a name from before I installed it?
No. Comparison starts at the first successful check on your watchlist. There is no back catalogue to retrieve.
If the name you need is a username rather than a display name, start with when a Roblox username changed. For the complete list of fields a monitor compares, see the Roblox profile tracker guide.
Published 6 September 2026. Endpoint behaviour checked against the Roblox Users API reference; product behaviour checked against RoTrail 1.4.0 source. Example names and times are fictional. Editorial method and corrections.