Project labels that actually stick
Stop naming things "final-final-v2". Generate sharp project labels — codes, slugs, tags, badges and codenames — in seconds. Type your project, pick a style, copy the winners. Everything runs 100% in your browser: no sign-up, no server, nothing stored.
A few plain words is perfect — "client onboarding portal".
Generate a batch, keep the two or three you love.
Code = PRJ-042 Website Redesign. Slug = website-redesign-007. Tag = #WebsiteRedesign. Badge = [CORE] Website Redesign. Codename = Amber Falcon.
Case applies to slugs and tags. Numbers keep labels unique.
Your labels will appear here — click any label to copy it.
Honest limits — read before you use these
- Labels are suggestions, not a system. The generator makes great individual labels, but a team needs one agreed convention — see our naming conventions guide before rolling these out.
- Check for collisions. Generated codes use random numbers; verify a code is not already taken in your tracker, repo, or drive before adopting it.
- Codenames are for internal use. Fun codenames are great for teams, but use descriptive labels for anything clients or the public will see.
- Nothing is stored. Labels exist only in your tab — copy or download them now if you need them later.
How the workbench works
No accounts, no network calls, no fine print. A small JavaScript file on your device does everything.
Pick a style
Five label styles cover every context: codes for trackers, slugs for URLs and folders, tags for social and docs, badges for boards, codenames for secret projects.
Stays on your device
Generation, copying and the .txt download happen locally. No backend, no database, no analytics. Close the tab and the labels are gone — we never see them.
Copy & ship
Click any label to copy it solo, grab the whole batch, or download a .txt. Paste into Jira, Notion, GitHub, Slack, or your file system.
When labels earn their keep
A good label is a tiny piece of infrastructure. These are the moments it pays off.
Team projects
Shared codes like PRJ-042 give everyone one unambiguous way to refer to a project across chat, docs and tickets. No more "which redesign do you mean?"
Files & folders
Consistent slugs (website-redesign-042) sort properly, survive every operating system, and make search actually find things.
Client-facing names
Internal codenames are fun for the team, but clients deserve descriptive labels. Generate a code for tracking, then give the client a plain-English name.
Labels are half the battle. Conventions are the other half.
Learn the naming rules that keep a whole team consistent — prefixes, casing, dates, and the mistakes to avoid.
Quick answers
What is a project label? +
A project label is a short, consistent name or code used to identify a project across tools — like PRJ-042 in a tracker, website-redesign as a folder name, or #WebsiteRedesign as a tag. Good labels are unique, searchable and unambiguous.
What label styles does LabelLab make? +
Five: codes (PRJ-042 Website Redesign), slugs (website-redesign-007), tags (#WebsiteRedesign), badges ([CORE] Website Redesign) and codenames (Amber Falcon). See the label styles guide for when to use each.
Is LabelLab really free? +
Yes. Unlimited labels, no account, no paywall. Everything runs in your browser, so there is nothing to charge for — and nothing to track. Details in our privacy page.
Can I use these labels commercially? +
Yes. Generated labels are yours to use however you like, including client and commercial work. No attribution required.
Will the codes be unique? +
Codes use random numbers from crypto.getRandomValues(), but randomness is not a uniqueness guarantee. Always check a code against your existing projects before adopting it — the honest-limits box above says the same.
Do you store my project names? +
No. The generator runs entirely in your browser. Nothing is sent to a server, no cookies are set by the tool, and nothing is tracked.
Label guides
From first principles to team-wide systems: everything about naming projects well.
60+ label ideas
Ready-made label patterns for launches, clients, internal tools, events and side projects.
Read guide → GuideNaming conventions
The team-wide rules: prefixes, casing, dates, and the five mistakes that break systems.
Read guide → GuideLabel styles compared
Codes vs slugs vs tags vs badges vs codenames — what each is for and when to use it.
Read guide →