Place important badges near the project title
License, version, build status, coverage, and documentation are common choices.
Loading converter…
[](https://github.com/example/project)
Select a category such as License, Version, Build, Coverage, Documentation, Downloads, or Custom.
Enter the label and message, then choose the available color and style options.
If the badge should be clickable, enter the page you want readers to open.
Check the result, then copy the generated Markdown into your README or Markdown file.
| Badge Type | Common Use | Example |
|---|---|---|
| License | Show the project's open-source license | license: MIT |
| Version | Display a package or release version | version: v2.4.0 |
| Build | Show CI or build pipeline status | build: passing |
| Coverage | Display test coverage percentage | coverage: 92% |
| Documentation | Point readers to project documentation | docs: available |
| Downloads | Show package or release downloads | downloads: 10k |
| Custom | Display project-specific information | status: active |
License, version, build status, coverage, and documentation are common choices.
Link a version badge to releases, a documentation badge to the docs, or a build badge to the relevant CI workflow.
Using unrelated badge shapes and styles together can make the top of a README look cluttered.
The purpose of a badge should be understandable without inspecting its source code.
A badge can display correctly even when its link points to an outdated page.
If a badge does not render, open the generated image URL directly and verify that it returns a valid image.
A short row of useful badges is usually easier to scan than a long collection covering every project detail.
A basic badge uses standard Markdown image syntax: . For a clickable badge, place the image inside a Markdown link: [](TARGET_URL).
Yes. You can set the label, message, color, style, and other options available in the generator. You can also add a destination URL when the badge needs to be clickable.
Yes. Add a destination URL to the badge, and the generated Markdown will use the image-inside-a-link format.
Yes. Standard Markdown image and link syntax is supported by many Markdown platforms and documentation systems. The exact result can vary depending on whether the platform allows externally hosted images.
Shields.io provides badge images that can be embedded in Markdown. A Shields.io-compatible URL can be used as the image source in standard Markdown badge syntax.
Open the image URL directly and check whether it returns a valid image. If it works there, check whether your Markdown platform allows remote images. For a clickable badge, also test the destination URL separately.
Last updated: Category: Markdown Generators