How does Nanotype's share link work?
Updated
Nanotype's share link works by embedding the text inside the link itself rather than storing it on a server. When you create a share link, the text is encoded into the URL, so anyone who opens that link can read the content without Nanotype keeping a copy on its side. This fits the site's stated design: text stays in your browser, the editor works offline, and "a share link carries the text inside itself."
What "carries the text inside itself" means
Most sharing tools work like this: you upload text to a server, the server gives you a short link, and the recipient's browser fetches the text from that server. Nanotype's description points to a different model. The link is the container. The text travels as part of the URL, so opening the link reconstructs the content in the recipient's browser.
That has a few practical consequences:
- No server-side storage is implied. The site's description says text stays in your browser and the share link carries the text inside itself. Nothing in the available material says Nanotype stores your shared text on its servers.
- The link is the text. Anyone holding the link holds the content. There is no separate permission check or account gate described.
- The editor remains usable offline. Since the text lives in your browser and the link embeds it, the core editing and sharing flow does not depend on a server round-trip for the text itself.
What a recipient needs to open the link
A recipient needs two things:
- The full link, unmodified. Because the content is encoded in the URL, any truncation, line break, or character change can corrupt or break the text. Copy the entire link, not a shortened display version.
- A browser. The link opens in a web browser, where the text is reconstructed for reading or editing. No account or login requirement is mentioned in the available material, but that is an absence of information, not a confirmed guarantee.
If the link is very long, that is expected: the text is inside it. Long links can be awkward in chat apps or email clients that wrap or truncate URLs, so verify the link arrives intact before relying on it.
Cautions before sharing sensitive text
Because the link contains the text, treat the link itself as the sensitive item:
- Anyone with the link can read the content. There is no described access control beyond possession of the link. Share it only with people you would trust with the text itself.
- Links can be forwarded, logged, or synced. Chat history, email archives, browser sync, and clipboard managers may retain the URL. If the text is confidential, consider whether those copies are acceptable.
- There is no described revocation. The available material does not mention an option to disable a link or expire it. If you need to limit access after sharing, that may not be possible through the described feature.
- Avoid sharing secrets, credentials, or personal data through a link whose contents travel in the URL.
Quick check before you share
| Question | What to do |
|---|---|
| Is the text sensitive? | Share only if you accept that anyone with the link can read it |
| Will the link survive the channel? | Paste it somewhere and confirm it is complete and clickable |
| Do you need to un-share later? | No revocation is described, so decide before sending |
| Does the recipient need an account? | None is mentioned; a browser is the stated requirement |
For everyday plain text and Markdown, the embedded-link approach keeps sharing simple and consistent with Nanotype's privacy-oriented design. For anything confidential, the link is only as private as the channel you send it through.