There are four ways to send somebody a character you made, and they are good at different things. Picking the wrong one is why characters so often arrive as a picture nobody can edit.
A share link
The character is stored inside the URL, so opening the link reopens the exact character in the editor — no upload, no account, nothing stored on a server. This is the right default for sending to one person, and the only option that lets them immediately start changing things.
The one caveat is length. The link is long enough that some chat apps wrap or truncate it. If it arrives broken, send the code instead.
A character code
The same information without the URL around it — short, unambiguous and safe to paste into a forum post, a comment or a game chat. The recipient pastes it into Load code in the editor. Use this anywhere a long link is likely to be mangled, and for anything you want to keep in a note for yourself.
An image
For actually using the character: a profile picture, a post, a video. An image cannot be edited back into a character, so send it alongside a code rather than instead of one. Seesaving a character as an image for which format to pick.
A recipe
The full settings list, or the numbered walkthrough. This is what you send when the other person is rebuilding the character somewhere else — on a console, or in a different creator with its own parts. It is the slowest to apply and the only one that crosses systems.
Which to use
- Sending to a friend to edit: share link.
- Posting publicly: code plus an image.
- Keeping it for yourself: code, saved somewhere outside the browser.
- Rebuilding on a console: recipe.
Making a character last
Saved characters live in this browser's local storage, so clearing site data removes them, and they do not follow you to another device. Anything you would be annoyed to lose should have its code copied somewhere durable. The code is the entire character — paste it back and it returns exactly, on any device.