Building a static Shields.io badge that displays your NBA 2K26 badge perks takes four inputs and zero memorization of path escaping rules. Open the Badge Generator, type the short label that should appear on the left side of the badge, enter the perk name or summary on the right side, pick a color by name or hexadecimal value, and optionally add a Simple Icons slug for a logo. The tool assembles the correct Shields.io URL by doubling literal dashes and underscores, URL-encoding other special characters, and appending supported options such as style, label color, and logo through proper query parameters. The same canonical URL is then reused to produce three ready-to-paste snippets: a direct image URL, a Markdown image link, and an HTML img tag with an escaped alt attribute. Because generation happens entirely client-side except for the remote preview image, no registration or login is required, and the form data is not posted to Lizely.
Why the URL structure is the real friction
The Shields.io static badge path separates the left label, the right message, and the color with dashes, and uses underscores in place of spaces. That convention is clean until the perk name you want to display already contains a dash, an underscore, or another special character. A perk such as "Limitless Range" looks harmless until the URL parser sees the space as the underscore rule and reads "Limitless" plus "Range" as two distinct badge parts. A perk such as "Catch-&-Shoot" looks like four segments. Writing the URL by hand means remembering that literal dashes must be doubled to "--", that underscores must likewise be doubled to "__", and that everything else needs to be percent-encoded. The query parameters for style, label color, and logo also have to be added in the correct order without contaminating the path. When the badge does not render as expected, the only debugging tool is staring at the URL and trying to guess which rule was missed.
This is exactly the friction Badge Generator removes. You type the visible text exactly as you want it to appear, choose a color from the list or paste a hex value, optionally enter a Simple Icons slug such as "nba", and the generator handles every escaping decision. The live preview is requested from Shields.io using the URL it just built, so what you see is what the destination will see. If a perk contains a literal dash such as "Catch-&-Shoot", the tool doubles it; if it contains an underscore such as "Hot_Zone", the tool doubles that too; if it contains a colon, a slash, or a non-ASCII character, the tool URL-encodes only what is necessary to keep the path parseable. The escaping behavior is described in the Shields.io static badge reference, and the generator follows those rules rather than improvising.
Build a 2K26 badge perks badge step by step
- Open Badge Generator and locate the Label field. Type the short left-side text, such as "Perk", "NBA 2K26", or "MyCAREER Build".
- Move to the Message field and type the right-side text exactly as it should appear. A single perk becomes "Limitless Range". Multiple perks can be combined with a literal pipe or slash as long as the visible text is what you want, but remember that any literal dash or underscore inside the message is doubled automatically.
- Pick a badge color. Choose a named color from the dropdown, such as "blue", "brightgreen", or "orange", or paste a three- or six-digit hexadecimal value with or without the leading hash. The leading hash is stripped before the URL is built.
- If your perk references a recognizable brand, category, or platform, enter the Simple Icons slug in the Logo field. "nba" is a valid slug for the NBA logo. Leave it blank if no logo is appropriate.
- Select a supported style from the available options. The default "plastic" style has the familiar rounded look; "flat", "flat-square", "for-the-badge", and "social" are the other documented Shields.io styles.
- Optionally set a separate Label color so the left segment stands out from the right segment when both halves need to be visually distinct.
- Watch the preview area. The preview image is fetched from Shields.io using the URL the tool just constructed, so any escaping mistake shows up immediately as a broken or wrong image.
- Copy the image URL, the Markdown snippet, or the HTML snippet and paste it into your README, GitHub profile, gaming wiki, or release notes.
- Open the destination to confirm the badge renders at the size you expect. If the target platform proxies remote images, clear that cache before assuming the change did not take.
Display NBA 2K26 badge perks on a README, profile, or wiki
To publish a specific NBA 2K26 badge perk such as "Limitless Range" on a GitHub profile README, follow these concrete steps rather than the generic flow above:
- Decide on a label that frames the badge. "NBA 2K26" reads cleanly on the left and gives context to anyone scanning the profile.
- Type the perk name in the Message field using the official game spelling, including capitals and any hyphens. Treat the Message field as the literal visible string, not as a Markdown snippet.
- Choose a color that reflects tier or category. "brightgreen" works well for elite-tier perks, "yellow" for gold-tier perks, and "orange" for build-defining perks. Hex values such as "#f7b500" are accepted and normalized before the URL is built.
- Add the Simple Icons slug "nba" to the Logo field so the badge carries the league's logo, or leave it blank if you want a plainer look that matches the rest of your README.
- Pick "flat" or "flat-square" if your README uses many inline badges. "plastic" remains the most recognizable look for a single hero badge.
- Copy the Markdown output. For a GitHub README the snippet takes the form .
- Paste it into the README, ideally grouped with the build name, platform, and current season so the perk is not floating without context.
- Repeat the process for each perk you want to highlight. Keep the Label identical across the set so the badges line up visually when stacked.
- Wrap the badges in a short paragraph that explains what each perk does. Static badges cannot carry the full meaning on their own, and color alone should never be the only signal of a tier.
For a multi-perk summary on a gaming wiki or personal site:
- Pick a label that frames the build, such as "Build", "MyPlayer", or "Season 1".
- In the Message field, list the perks separated by a literal pipe character or another delimiter that fits your layout. Validation still requires visible text and a practical length limit, and every literal dash or underscore in the combined message is still doubled automatically.
- Choose a single color for the summary, or vary the color per perk to convey tier differences.
- Use the HTML output rather than Markdown so you can control alignment, spacing, and grouping on a custom page, and so the alt attribute is available for assistive technology.
- Add a meaningful alt description in the surrounding HTML so screen readers describe the perks, not just "badge".
Choosing between URL, Markdown, and HTML output
| Output | When to use it | Format produced |
|---|---|---|
| Direct image URL | Embedding a badge in a platform that accepts a remote image source but does not parse Markdown, or when you want to inspect the exact address Shields.io will receive. | https://img.shields.io/badge/... |
| Markdown | Pasting into a GitHub or GitLab README, an issue template, a pull request description, or any other Markdown document. GitLab's project badge documentation covers destination-side rendering. |  |
| HTML | Embedding in a web page, a dashboard, a custom blog template, or anywhere that accepts markup and benefits from an explicit alt attribute. | <img src="..." alt="..."> |
The three snippets are derived from the same canonical URL, so once the preview matches your expectation, every output will render the same image. Switching destinations does not require rebuilding the badge — only choosing the snippet that matches the host's syntax. Markdown is the safest default for repository documentation and profile pages that support it. HTML is the right choice when the page needs accessible alt text or when Markdown is disabled. The raw URL is useful for debugging and for hosts that only consume a direct image link.
Validation, limits, and the static badge caveat
Badge Generator is intentionally strict about input. Empty labels and empty messages are rejected. Control characters are rejected because they can corrupt the URL or produce invisible text. Colors are accepted in their compact named form or as three- and six-digit hexadecimal values, with an optional leading hash stripped before the path is built. Logo values must look like a Simple Icons slug; arbitrary URLs or punctuation will fail validation. These checks catch the common typing mistakes that produce broken badges, but they do not pretend to verify whether every named color or every slug actually exists on Shields.io or Simple Icons. If a logo fails to appear in the preview, verify the slug against the current Simple Icons catalog. If a named color renders differently than expected, the same color name may map to a different shade on Shields.io than it does in CSS.
Generation is entirely client-side. No form data is posted to Lizely; only the preview image is requested from Shields.io, which receives the URL you built. No account is required, and badge history is not saved, so a refresh is the simplest way to start over. The tool stays entirely client-side except for the remote preview image.
A static badge is presentation, not proof. A manually entered "passing", "secure", "100% coverage", or "Limitless Range" message does not verify a build, an audit, a coverage report, or an in-game unlock. Use static badges for stable labels, links, versions, or statements you are prepared to maintain. For automatically changing facts, use a badge backed by the relevant CI system, package registry, or verified endpoint instead. Always add surrounding prose or a meaningful alt description where context matters, because color alone should never carry the full meaning. Earning the actual NBA 2K26 badge perks still happens inside the game; this tool only helps you display them.