Code sharing
How to share code with a raw paste link
A normal paste is comfortable for people to read. A raw link gives tools the plain text. With both forms available, one snippet can work in a code review, support thread, command, or document.
Rendered paste versus raw link
The rendered paste page is designed for a person. It can show syntax highlighting, a title, and the surrounding share controls. The raw URL returns the paste content without the presentation layer, which is useful when a command, script, or documentation system needs plain text.
Keep the rendered URL as the link you normally send to another person. Use the raw version only where plain text is genuinely more useful. This gives readers a clear page without making automated workflows scrape HTML.
Create a useful code paste
- Open Pastes in smpl.gg and create a new paste.
- Give it a specific title that describes the snippet, error, or configuration.
- Choose the closest language so the rendered page can highlight the code correctly.
- Select public visibility only for material you intentionally want discoverable. Use unlisted for ordinary review and support links.
- Publish the paste and open its share page to verify formatting and line breaks.
- Choose View raw when a tool or command needs the plain-text version.
Use raw links responsibly
A raw link is convenient in documentation, issue reports, setup scripts, and command-line examples. Before depending on it in automation, remember that removing the paste, expiring the share, or changing its access controls can make that URL unavailable.
For long-lived software dependencies, a version-controlled repository and a pinned revision are usually a better source than a mutable paste. Raw pastes are best for collaboration, troubleshooting, examples, and intentionally lightweight distribution.
Never paste secrets
Review the content before publishing. Remove API keys, session cookies, passwords, private URLs, personal data, database connection strings, and environment variable values. Unlisted does not mean secret; anyone with the URL can redistribute it.
If a secret is pasted accidentally, delete the paste and rotate the exposed credential immediately. Removing the page does not prove that nobody copied or cached the value while it was accessible.
Make troubleshooting easier
Include the smallest complete example that reproduces the problem. Add the relevant error and enough surrounding code to show how the failing value is created, but remove unrelated application code and customer data.
Use the paste title or accompanying message to state the runtime, version, and expected behavior. Good context makes the snippet searchable for the recipient and reduces the back-and-forth needed to understand it.
Frequently asked questions
What is a raw paste link?
It is a URL that returns the paste body as plain text instead of rendering the normal syntax-highlighted share page.
Should I make a code paste public?
Only when you intentionally want it discoverable. Use unlisted for routine reviews and support, and never rely on unlisted visibility to protect secrets.
Can I use a raw link in a script?
Yes, but remember that deleting, expiring, or restricting the paste can break that dependency. Use version control for durable software artifacts.
What should I do if I pasted an API key?
Delete the paste and rotate the key immediately. Treat the credential as exposed even if the link was unlisted.