DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to share a finished avatar as one .mavatar file with Mesh Avatar Studio

Export your saved avatar as a single file that another person can import into Studio.

  • Content
  • Intermediate
  • 15 minutes
  • From the README
  • Any agent

Who it is forA creator who wants to send a finished avatar to a collaborator or another Studio user.

The problemMoving an avatar project between machines means copying rigs, layers, expressions and metadata correctly.

The outcomeOne .mavatar file that a recipient imports as a new project folder under projects/.

What you need first

  • Node.js 22.17+ and Git
  • A front-facing, head-and-shoulders PNG with a transparent background (best results)
  • Claude Code or Codex, if an agent will prepare the avatar
  • Optional: uv, Python and Playwright Chromium for agent layer rebuilds and motion review
  • A webcam and microphone, only for the Live page

Steps

  1. Run npm run dev and open your project in the editor
  2. Choose Export .mavatar, keeping Include source image on if the recipient should edit it
  3. Send the downloaded file to the recipient
  4. On the recipient's machine, run npm run dev, choose Open project, then Import .mavatar and select the file

Prompt for your agent

In the mesh-avatar-studio repository, export the project <project name> as a .mavatar file using the editor. Expect a downloaded archive under 128 MiB. Verify that it imports as a new folder under projects/ and plays in the preview.

Caveat. Without the source image the imported avatar can play but cannot be edited or rebuilt, and import requires npm run dev.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page