Project Title
Write a short description of your project here. Use the toolbar above to format text just like in a word processor.
Pick the folder that contains your project. We'll list its files so you can link to them or embed images while you write your README.
When you pick a folder your browser will ask to view or upload files — click Allow or Upload to continue. Your files stay on your computer.
Write a short description of your project here. Use the toolbar above to format text just like in a word processor.
Choose how many rows and columns to add, then insert the table into your document.
Pick a starting point, then tweak it to fit your project. Choosing one replaces the current document.
GitHub surfaces these files in its UI. Fill in the details, pick which to create, and they'll be written into your repo.
Push your README straight to a repo — no download, no backend. You'll need a fine-grained Personal Access Token with Contents: Read and write permission, scoped to the repo(s) you want to publish to.
A Personal Access Token (PAT) is like a scoped password that lets this app commit your README to a repo on your behalf. It works entirely from your browser — there's no server involved. Takes about a minute to set up.
Go to github.com/settings/personal-access-tokens/new (Or on GitHub: your avatar → Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token.)
readme-editor.Under Repository access, choose Only select repositories and pick the repo(s) you'll publish your README to. This limits the token so it can never touch anything else.
Under Permissions → Repository permissions, find Contents and set it to Read and write. Leave everything else as “No access”.
Click Generate token, then copy it (it starts with github_pat_…).
Copy it now — GitHub only shows it once.
README.md, and click Publish.GitHub README Editor is a free, browser-based tool for writing and publishing GitHub README files — with a word-processor-style editor, a live Markdown preview, ready-made templates, badges and widgets, license and community-health file generators, and one-click publishing straight to GitHub.
This project is free to use and its source code is openly available on GitHub. You're welcome to read it, learn from it, and contribute.
View source on GitHubMIT License + Additional Restrictions — © 2026 Pavaris Pobhirun. Free for personal use and as a component of commercial projects; you may not sell the software itself, and you must credit the author.
MIT License + Additional Restrictions
Copyright (c) 2026 Pavaris Pobhirun
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, subject to the following conditions:
Credit/Attribution: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. You must provide clear credit to Pavaris Pobhirun when using this software.
Non-Profit Restriction: You are strictly prohibited from selling this Software as a standalone product or incorporating it into a paid package/service for direct profit.
Usage: You are free to use this software for personal projects or as a component within a commercial project, provided that you do not sell the software itself.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.