Keep the goal narrow
Share one task-specific artifact: Readable snippets with language-aware highlighting and raw links.
A pastebin workflow for sharing code snippets
A useful code paste preserves exact whitespace while giving the reader enough context to understand, run, or review the snippet. It is best for one focused artifact, not a substitute for a multi-file repository.
Share code at a glance
Use these three checks before you turn share code into a link for another person.
Start with the least exposure
Recommended first step: Select the exact language mode
Remove risky details
Before upload: Review the share code checklist below to replace live values while preserving the context a recipient needs.
Share code tip: How to share code online adds this format-specific context: Build a focused, formatted example that a reviewer can reproduce.
Share code workflows
A well-scoped share code artifact preserves the task-specific context below and can expire when that task ends.
Minimal reproductions
Reduce the problem to one runnable snippet, then add the runtime version, exact command, expected result, and actual result.
Code-review excerpts
Share the relevant function or diff with a stable line reference while the durable change remains in version control.
Interview exercises
Use an expiring unlisted link for a bounded exercise, and remove company data, private test fixtures, and hidden credentials.
Recommended paste settings
- 1Select the exact language mode
- 2Use unlisted visibility for a review
- 3Set expiry to the review window
- 4Include runtime and reproduction steps
What not to include
Do not paste repository secrets, proprietary modules you cannot distribute, or a multi-file project that needs build assets. Use a repository or approved review system for those.
For share code, a made-up but representative example is safer than a production export. Expiration can end future access to the source link, but it cannot recall a recipient’s copy.
Compare privacy controls →Use encryption when share code must not be readable in storage
For a private share code artifact, encrypted mode applies AES-GCM in the browser before upload. Its key stays after # in the share URL and outside the normal server request.
Understand client-side encryption →BEFORE UPLOADReadable content
→AES-GCM
IN STORAGEEncrypted bytes
Share code questions
Practical answers about the access, retention, and context choices for share code.
Does syntax highlighting change my code?+
No. It changes only how tokens are displayed. The raw view preserves the submitted text.
When should I use a repository instead?+
Use a repository when the example needs multiple files, dependencies, version history, tests, or ongoing collaboration.