# Sharing a snippet

> Turning playground code into a link, why signing in makes it permanent, what happens when somebody opens yours, and the one thing you cannot do afterwards.

Source: https://www.revquix.com/docs/projects/sharing-a-snippet
Last verified: 2026-09-04

---

**Share** in the playground turns what is in the editor into a link anybody can open. No account
needed, and the person opening it needs one even less.

The link carries the code, the language, and the input you had in the Input panel.

## Signing in makes the link permanent

This is the whole difference, and it is worth knowing before you paste a link into something durable.

|                            | Signed out  | Signed in |
| -------------------------- | ----------- | --------- |
| The link lasts             | **90 days** | forever   |
| Links you can create a day | 50          | 200       |

The dialog tells you which you are getting. It shows an expiry date **only when there is one** -
rather than showing a date to somebody whose link will never expire.

> **Warning** - The expiry is fixed when the link is made
>
> It is stamped at creation, not worked out when somebody opens it. So signing in afterwards does not
> extend a link you already shared, and a link you made while signed out keeps its 90 days.
>
> If a link matters - it is in a README, a job application, a blog post - make it while signed in.

## What somebody sees when they open yours

The snippet loads into a playground with a quiet line saying the code belongs to somebody else.

That line matters more than it looks: without it a share link is indistinguishable from your own
playground, and the visitor presses Reset expecting their own file back.

> **Note** - Opening a snippet does not touch the visitor's own work
>
> Their draft is left completely alone while they are reading yours. Somebody with an hour of work in
> the editor can safely click a link a friend sent them - which is the entire reason that rule exists.

The **runtime version captured when you shared** is shown, not today's. A snippet shared before a
language was updated can still say what its author actually ran.

## Forking

**Fork** copies the snippet into the visitor's own playground so they can edit and run it as their
own.

It is the one action that writes to their drafts, so when they already have work in that language it
asks first rather than overwriting it.

## Reset

On a shared snippet, Reset restores **the author's code and their input** - not a blank starter file.
"Undo my edits" there means back to what you were sent, which is the only reading that makes sense
when you are looking at somebody else's work.

Fork first if you intend to keep your changes.

## What you cannot do afterwards

> **Warning** - There is no list of the links you have created
>
> The product has no "my snippets" screen, so there is no way to look back at what you have shared or
> to take a link down.
>
> For a signed-out link that resolves itself in 90 days. **A signed-in link does not** - it is
> permanent, and permanent means permanent. So think about the contents before sharing: a snippet with
> a key, a password or an internal endpoint in it is out there for good.

## Snippet or project?

|                                                | Use a snippet | Use a project |
| ---------------------------------------------- | ------------- | ------------- |
| One file                                       | ✓             |               |
| Several files, or a folder structure           |               | ✓             |
| Somebody should be able to run it in one click | ✓             | ✓             |
| You want to keep working on it                 |               | ✓             |
| You want to take the share link down later     |               | ✓             |

Sharing a project is covered in [sharing a project](https://www.revquix.com/docs/projects/sharing-a-project), and it has the
visibility controls a snippet does not.

## Related

- [The playground](https://www.revquix.com/docs/projects/the-playground) - Where snippets come from.

- [Sharing a project](https://www.revquix.com/docs/projects/sharing-a-project) - The version you can unshare.