The Roblox Developer Portfolio Guide

In most creative industries, a portfolio is something a hiring manager clicks into deliberately — they've already decided you're worth ten minutes of attention. Roblox development doesn't work that way. The first contact almost always happens inside a Discord server: a recruiter or studio lead scrolling a portfolio channel, skimming a pinned thread, or clicking a link someone dropped in a collaboration post. By the time they've decided whether you're worth a reply, they've looked at your link for somewhere between five and fifteen seconds. The link is not an accessory to your portfolio — in this niche, the link effectively is the portfolio, and everything about how you build one should be designed around that fact rather than around what a traditional design portfolio looks like.

This guide covers what to include, what to cut, why proof consistently beats visual polish in this specific market, and where to actually put the link so the right people see it.

It's also worth being honest about what a portfolio is actually competing against in this niche. A studio lead scrolling a Discord portfolio channel is looking at dozens of links in a single sitting, most of them structured the same way — a banner image, a list of bullet points, a "DM me" at the bottom. The developers who get replies aren't the ones with the nicest banner; they're the ones whose link answers the buyer's actual question — can I trust that this person built what they say they built — faster than the next link in the scroll.

What to include

A Roblox developer portfolio that converts a scroll into a reply does a small number of things well rather than a large number of things adequately. Five elements do almost all of the work.

Games with real visit counts

Not a screenshot of a visit counter — a link to the actual game, or a number that a viewer could go verify themselves in under a minute. A static number in an image can be edited before the screenshot is taken; a linked game page cannot lie about its own current visit count. If you've only worked on games with modest numbers, list them anyway with honest counts — a real 40,000-visit game is more useful evidence than an unverifiable claim about a game with millions. Starting from zero shipped games entirely is a different problem with its own playbook — see how to build a portfolio with no experience yet.

Specific contributions per game

"Worked on this game" tells a viewer nothing about what you can do. "Built the inventory and trading system" or "modeled and rigged the four playable characters" tells them exactly what to expect if they hire you for the same thing. List systems, not vibes, and be precise enough that someone who worked on the game with you would recognize the claim as accurate. If scripting is your specialization, see what a strong scripter portfolio actually lists down to specific systems and code samples.

Your specialization, stated plainly

Scripter, builder, modeler, UI designer, or animator — say which one you are in the first line, not the fifth. Recruiters and studio leads are usually filtering for a specific role; if they have to read three paragraphs to figure out whether you're a scripter or a builder, most will move on before finding out.

Rates or a rate range

Even an approximate range saves both sides a round of DMs that ends in a mismatch. Someone with a $3,000 budget and someone with a $50 budget should be able to self-select before messaging you, not after.

One clear way to reach you

A Discord handle, a DM-open policy, an email — pick one primary channel and make it unmissable. A portfolio that makes a viewer hunt for how to actually contact you loses most of the people who were ready to reach out.

What to cut

Just as important as what to include is what to remove, because everything you add past the essentials dilutes the parts that actually prove something.

Participation-trophy jams

A game jam entry you built alone in 48 hours that nobody played is not evidence of professional-grade work, and listing five of them next to your real shipped projects makes the real projects look smaller by association. Keep at most one jam entry, and only if it demonstrates a skill your shipped work doesn't already show.

Unverifiable claims

"Helped build a game with over 1 million visits" with no game linked is worse than saying nothing — it invites the exact skepticism this whole guide is about, and a careful buyer will simply skip past it rather than ask you to prove it.

Walls of screenshots

Ten UI mockup screenshots with no context about which shipped or what role you played on the team is a scroll-past. Two or three screenshots tied to a named, linked game with a specific credited contribution outperform a gallery of disconnected images every time.

Proof beats polish

It's tempting to spend your energy on visual presentation — a slick personal site, custom fonts, animated transitions. In most creative fields that pays off. In Roblox hiring, it mostly doesn't, because the actual bottleneck for buyers isn't finding developers who present well — it's finding developers whose claims hold up. A plain page listing two API-verified games with accurate visit counts and a collaborator attestation will out-convert a beautifully designed page listing unverifiable claims, because the buyer's core question is never "does this look professional" — it's "did this person actually build what they say they built."

Picture the comparison a buyer is actually making, side by side: one portfolio shows a custom-designed page with a hero image, testimonial quotes with no names attached, and a claimed visit count typed into a paragraph. The other shows two games, each linked, each showing a visit count that matches what Roblox itself reports, with one collaborator confirming "built the shop and inventory system" next to their own name. The second one wins almost every time, even though it took a fraction of the design effort, because it removes the one thing every buyer in this market is bracing against — being lied to by a portfolio that looks legitimate.

This is the entire reasoning behind how Roport profiles are built: games pull live visit counts and metadata straight from the Roblox API rather than a hand-typed number, and attestations let named collaborators vouch for a specific contribution on a specific project — not a generic endorsement, a claim tied to one game that someone else is putting their own name behind. See how buyers actually run verification before they pay for work, and design your portfolio to pass that check on the first look rather than requiring a back-and-forth to prove yourself. Roblox's own documentation on Studio collaboration tools is worth understanding too, since how you collaborated on a project — solo edit access versus a shared team build — affects what you can honestly claim credit for.

Distribution — where the link actually needs to live

A great portfolio nobody sees does nothing. Distribution in this niche means putting one canonical link in every place a buyer might already be looking, rather than maintaining several different profiles that drift out of sync with each other. For a full breakdown of every channel and how to post in each, see where to post your Roblox portfolio, and for choosing which platform to host the canonical link on in the first place, see the best Roblox developer portfolio sites.

Portfolio Discord servers

Communities like HiddenDevs and smaller genre-specific servers have dedicated portfolio or showcase channels — this is where the highest volume of cold discovery happens, so your link belongs pinned in your profile or posted in the relevant channel, not buried three messages deep in a thread from months ago.

DevForum signature

Every post you make on the Roblox DevForum carries your signature with it. If you're active in the collaboration category or answering scripting questions, a signature link means every helpful post doubles as quiet distribution.

X bio

If you post progress clips or devlogs, the bio link is what turns a viral clip into an inbound message. Put it there even if X isn't your primary channel — it costs nothing and catches traffic you wouldn't otherwise see.

One canonical link, everywhere

The common failure mode is scattering slightly different portfolios across Discord, DevForum, X, and a personal site, each one out of date in a different way. Pick one link — a profile on Roport, on a personal site, wherever — keep it current, and point every channel at that same URL. Browse games already indexed on Roport to see how other developers structure their credited work, and check what it costs to run a profileif you're deciding whether to consolidate onto one platform for good.

Frequently asked questions