Go Paste
Paste Go Code and Panic Stack Traces, Highlighted
Share Go code snippets with syntax highlighting. Stack traces, struct definitions, gofmt'd functions — all preserved.
The two things Go developers most often need to share are gofmt'd source and panic stack traces — and both are exactly what chat tools wreck. A goroutine dump is a tall, indentation-sensitive block where every line matters for diagnosis; paste it into Slack and the alignment collapses, the goroutine N [running]: headers blur into the frames, and the person reading it can't tell which frame is yours versus the runtime's. files.link renders Go through highlight.js so struct definitions, interface satisfaction, channel ops, struct tags, error wrapping, and modern generics all keep their shape, and a pasted panic trace stays readable line by line.
For a stack trace specifically: paste the full panic: ... block and select Go (or plain text if the trace is mostly addresses and paths). The frame structure — function name, then the file:line on the next line — survives intact, so a reviewer can walk from the panic site down through the call chain without reconstructing line breaks by hand. That's the difference between someone diagnosing your deadlock in two minutes and asking you to re-send it 'properly formatted.'
For source, the common cases all render cleanly: a gofmt-aligned struct with tags, a generic constraint with [T any], a select over channels, a table-driven test, or a snippet showing how an error is wrapped with %w. Because it's a paste and not a compiler, files.link doesn't run the code — when you want to actually execute something, the Go Playground is the tool; when you want to *share* the source or a crash, a paste link is.
No signup to create or read, so a teammate opens it instantly. Anonymous pastes hold 100KB and expire after 24 hours; a typical stack trace or snippet is well under that. Sign in for 1MB — handy for a long verbose-test dump or a big goroutine trace from a hung service — and an expiry of your choosing up to permanent for an example you'll link from a docs page or an issue. A Gist demands a login to post; a Slack block can't be opened outside the workspace. A paste link just works and keeps the structure.
Benefits With No Complexity
Global CDN delivery
Edge-cached worldwide
Signed-URL security
What You Get
Unlimited files
Unlimited storage
Public + Private storage
CDN ready links
Prepaid credits
More coming soon
How files.link Works
1. Upload
2. Copy
3. Use Anywhere
Why Developers Choose files.link
A Better Way to Store & Deliver Files
| GitHub Gist | Go Playground | Slack code block | files.link | |
|---|---|---|---|---|
| Create + read with no signup | ||||
| Panic stack traces stay aligned | ||||
| Generics / struct tags highlighted | ||||
| Compiles / runs the code | ||||
| Choose expiry (1h to permanent) |
Calculate Your Needs
Storage
Egress
CDN Bandwidth
Paste Go Code
- Global CDN delivery
- Edge-cached worldwide
- Signed-URL security
- Unlimited files
- Unlimited storage
- Public + Private storage
- No subscription — prepaid credits keep spend predictable