Frequently asked questions
Everything you might want to know about Gistly — from sharing a code snippet to the in-browser mock data generator. Can't find an answer? Email hello@gistly.dev.
- What is Gistly?
- Gistly turns any code snippet into a shareable gist. Paste your code into the editor, choose the language, indentation, and line wrapping, save it, and you get a permanent link you can share. It is a fast, focused alternative to a pastebin, built for developers.
- Is Gistly free to use?
- Yes. Creating, sharing, and viewing gists is completely free, and so is the in-browser mock data generator. There is no paid tier.
- Do I need an account to share a code snippet?
- No. You can create and share a gist anonymously without signing in. Signing in — with GitHub or Google — adds extra features: you can own your gists, keep them private, and create API keys for the HTTP API.
- How do I sign in to Gistly?
- Sign in with either your GitHub or Google account from the menu in the header. If both accounts use the same verified email address, they resolve to a single Gistly account, so your gists and API keys are the same whichever one you use to sign in.
- What is the difference between public, unlisted, and private gists?
- Public gists can be opened by anyone and may be indexed by search engines. Unlisted gists can also be opened by anyone with the link, but are never indexed. Private gists can only be viewed by you while you are signed in, and can only be read through the API using your own API key. You choose the visibility when you create a gist.
- Will my gists show up in search engines?
- Only if you mark them public. Public gists can be indexed by search engines and are listed in our sitemap. Unlisted and private gists are never indexed — an unlisted gist is reachable only by people you share the link with, and a private gist only by you.
- How do private gists stay private?
- Private gists are tied to your account and are only served to you when you are signed in — anyone else gets a "not found" response, so a private gist is never revealed to exist. Over the API, a private gist can only be read with your own API key. Session tokens and API keys are stored only as one-way hashes, never in plain text.
- Does Gistly have an API?
- Yes. The HTTP API at api.gistly.dev lets you read, list, update, and delete gists programmatically. Public and unlisted gists can be read without authentication; reading private gists and updating or deleting gists you own requires an API key sent as a Bearer token.
- How do I create an API key?
- Sign in with GitHub or Google, then go to Settings → API keys and create a key. The full key is shown only once, at creation, so copy it then — afterwards only a short prefix is stored for reference.
- What is the mock data generator, and where does it run?
- The mock data generator creates realistic JSON test data from a prompt, using a language model that runs entirely in your browser with WebGPU. Your prompts and the generated data never leave your device, and you can save a result as a gist. It needs a WebGPU-capable browser such as Chrome, Edge, or Safari 18+.
- How is Gistly different from GitHub Gist or Pastebin?
- Gistly focuses on sharing a single code snippet quickly, with per-gist control over language, indentation, and wrapping, plus public, unlisted, and private visibility. It pairs that with a simple HTTP API and an in-browser mock data generator, without the broader account and repository features of larger platforms.
- How do I report a bug or request a feature?
- Use the Feedback button in the site header or footer and choose whether to report a bug or request a feature. You do not need an account to send feedback, and you can leave your email if you would like a reply.