Skip to content
TextArray
100% local

humans.txt generator

Build a humans.txt credits file — TEAM, THANKS and SITE sections — from a simple list.

Input
Output
Related tools
Robots.txt generatorDeveloper tools
Sitemap XML generatornewDeveloper tools
vCard generatorDeveloper tools
CSP header generatornewDeveloper tools
Cron expression parserDeveloper tools
CSS formatternewDeveloper tools
humans.txt generator
robots.txt is for machines; humans.txt is its counterpart for people — a small plain-text file at /humans.txt that credits everyone who built the site. It is an initiative of humanstxt.org, and its charm is the simplicity: no markup, no schema, just labeled sections a curious visitor can read. This tool assembles the file in the standard shape from the least ceremony possible.
The team goes into the input, one person per line, as Name | Role | Location — the role and location are optional, and a bare name works. Each person becomes a Role: Name line with an optional From: line, inside the /* TEAM */ section. The thanks field takes a comma-separated list of names or URLs for /* THANKS */, and the site facts — language, doctype, the technology list for the Components line, and a last-update date — fill /* SITE */. Sections you leave empty are omitted entirely, so a solo project produces a compact three-line file rather than a scaffold of blank headings.
The output drops straight into your web root as humans.txt, next to robots.txt. Some sites also add <link rel="author" href="/humans.txt"> to their head — nice, but optional; the file's convention is the location itself.
Everything runs locally in your browser — the names and details of your team never leave your device.
FAQ
What is humans.txt actually for?
Credit. Websites are built by people, and humans.txt is the standing convention (from humanstxt.org) for naming them — team, contributors, tools — in a file any visitor can open. It has no SEO effect; it is a signature, not a signal.
Where do I put the file?
In the web root, as /humans.txt — the same place robots.txt lives. Serve it as plain text (UTF-8). Optionally add <link rel="author" href="/humans.txt"> to your pages' head so tools can discover it.
What if a person has no role or location?
Both are optional. A bare name gets the generic Team: label and no From: line. Use the pipes only for the parts you have — "Jana | Developer" and plain "Jana" are both valid input lines.
Is there a required format for the sections?
humans.txt is deliberately loose — the /* SECTION */ headings and indented Key: value lines are the humanstxt.org convention this tool follows, but no parser enforces it. Feel free to edit the output; anything readable is correct.
Is my team list uploaded anywhere?
No. The file is generated entirely in your browser and your team's details never leave your device.