I've been using GitHub Gists for years to share code, notes, and docs. They're incredibly useful but look pretty ugly.
I built gists.sh to fix that. Take any gist URL, replace gist.github.com with gists.sh, and get a beautiful version.
It renders each file type properly: Markdown with great typography, GFM alerts, table of contents, etc. Code with Shiki highlighting. JSON and GeoJSON as collapsible trees. CSV/TSV as sortable, searchable tables. YAML as navigable trees. ICS files as calendar event cards. Multi-file gists get tabs with a Pretty/Raw toggle.
You can customize with URL params (?theme=dark, ?noheader, ?nofooter, ?mono) and combine them.
I'm a designer as well, and I've just grown frustrated with gists looking this bad. gist.io [1] tried to fix this back in 2012 but only handled Markdown and has been dead for years.
There's also a raw content API (/api/raw/{id}) with proper Content-Type headers, useful for scripting or piping gist content into other tools.
My favorite use case right now: I often ask coding agents or my OpenClaw to create gists to share notes, code, or reports with me. So I built this to work well with agents too (there's a skill as well), so you can get the pretty gist version directly when you ask for one.
I've been using GitHub Gists for years to share code, notes, and docs. They're incredibly useful but look pretty ugly.
I built gists.sh to fix that. Take any gist URL, replace gist.github.com with gists.sh, and get a beautiful version.
It renders each file type properly: Markdown with great typography, GFM alerts, table of contents, etc. Code with Shiki highlighting. JSON and GeoJSON as collapsible trees. CSV/TSV as sortable, searchable tables. YAML as navigable trees. ICS files as calendar event cards. Multi-file gists get tabs with a Pretty/Raw toggle.
You can customize with URL params (?theme=dark, ?noheader, ?nofooter, ?mono) and combine them.
I'm a designer as well, and I've just grown frustrated with gists looking this bad. gist.io [1] tried to fix this back in 2012 but only handled Markdown and has been dead for years.
There's also a raw content API (/api/raw/{id}) with proper Content-Type headers, useful for scripting or piping gist content into other tools.
My favorite use case right now: I often ask coding agents or my OpenClaw to create gists to share notes, code, or reports with me. So I built this to work well with agents too (there's a skill as well), so you can get the pretty gist version directly when you ask for one.
No tracking, no sign-up, no data stored. Secret gists are noindex'd. Open source: https://github.com/linuz90/gists.sh
[1] https://news.ycombinator.com/item?id=4263437
Forgot to write, source is here: https://github.com/linuz90/gists.sh