README Generator
Fill in a few fields and get a well-structured README.md for GitHub, GitLab or npm: badges, table of contents, installation, usage, configuration, roadmap, contributing, license and contributors. Watch the rendered preview as you type, then copy or download it.
Last updated:
Project basics
Badges
About & features
Installation & usage
Roadmap & contributing
License, contributors & contact
How to use the README Generator
- Enter your project basics: name, one-line tagline and, optionally, the GitHub repository (user/repo) and package name. These power the badges and install commands.
- Pick badges such as license, build status or npm version and choose a badge style.
- Describe the project: what it does, key features, and add a screenshot or demo link.
- Fill in installation and usage: choose a package manager to prefill commands and paste a short code example.
- Add the rest: configuration options, roadmap, license and contributors. Empty sections are left out automatically.
- Check the preview, then copy the Markdown or download README.md into the root of your repository.
Recommended README structure
| Section | What to write | Needed? |
|---|---|---|
| Title and description | The project name and one sentence on what it does and for whom | Always |
| Badges | Build status, version, license: quick signals of health and maturity | Recommended |
| About / screenshot | The problem it solves, a screenshot or GIF, a demo link | Recommended |
| Getting started | Prerequisites and the exact install commands | Always for code |
| Usage | The smallest example that works when copied and pasted | Always for code |
| Configuration | Environment variables or options, with defaults | If configurable |
| Roadmap | What is done and what is planned (GitHub renders task-list checkboxes) | Optional |
| Contributing | How to propose changes; link to CONTRIBUTING.md for long guides | For open source |
| License | The license name and a link to the LICENSE file | Always for open source |
| Contributors, acknowledgements, contact | Credits and how to reach the maintainers | Optional |
GitHub Markdown quick reference
| Element | Markdown |
|---|---|
| Heading | ## Installation |
| Bold / italic | **bold**, *italic* |
| Inline code | `npm test` |
| Code block with highlighting | ```js … ``` |
| Link / image | [text](https://…),  |
| Badge with link | [](https://…) |
| Task list | - [x] done, - [ ] to do |
| Table | | A | B | then | --- | --- | |
| Centered block | <p align="center">…</p> (HTML is allowed) |
| Note callout | > [!NOTE] on the first line of a blockquote |
Tips for a README people actually read
- Lead with the value. The first two lines should tell a visitor what the project does and why they would use it.
- Make the first example copy-paste ready. Test the install and usage commands in a clean environment.
- Show, don't tell. A screenshot or short GIF explains a UI faster than paragraphs.
- Use relative paths for images and files inside the repository (
docs/screenshot.png) so they work on forks and branches. - Keep it current. Update the README in the same pull request that changes installation or usage.
Frequently asked questions
What should a good README include?
At minimum: the project name, a one-sentence description, how to install it, a short usage example and the license. Larger projects add badges, screenshots, configuration options, a roadmap, contributing guidelines and credits.
Where do I put README.md?
In the root folder of your repository. GitHub, GitLab and Bitbucket show it automatically on the project's main page, and npm displays the README of a published package.
How do the badges work?
Badges are images served by shields.io. Dynamic badges such as stars, license or build status read live data from GitHub, npm or PyPI each time the README is viewed, so they need the correct user/repo or package name. They only appear once the repository or package is public.
Why do table of contents links work on GitHub?
GitHub creates an anchor for every heading by lowercasing it, removing punctuation and replacing spaces with hyphens. The generator builds the table of contents with the same rule, so #getting-started jumps to the Getting Started heading.
Does the README include the full license text?
No. The README names the license and points to a LICENSE file, which is the convention. Create that file separately, for example with a license generator.
Is my project information uploaded?
No. The README is generated in your browser and the draft is only saved in local storage. Badge images in the preview load from shields.io like they would on GitHub.
Are all the tools on FreeToolCabin tested for quality and accuracy?
Yes! Every tool on our site undergoes automated Q/A testing in real browser environments to ensure high precision, correct output, and zero errors. If you happen to spot a bug or have a suggestion, please contact us at [email protected] and our team will review it right away.