Saved Outfits in Catalog Avatar Creator — Visibility, Not Saving & Fixes

Saved outfits raise three different questions, and this page answers all of them: can other players see your saves (privacy), why an outfit fails to save (the bug cluster), and the difference between saving and publishing that trips up most new players. All of it comes from community documentation, with the unverified parts marked.

Quick answer

Quick answer: saved outfits live in your in-game wardrobe. Whether other players can browse your saves is not documented (to be verified) — published outfits are the public ones. If saving fails: rejoin first, and try an unnamed save — community documentation reports named saves are the ones that break.

Save vs publish — the distinction that matters

Two different buttons, two different outcomes:

• Save puts the look in your private in-game wardrobe — yours to re-wear any time.
• Publish pushes it to the public community browser (the 50M+ outfit pool), generates a shareable outfit code, and starts counting try-ons toward the Outfit Designer role.

If an outfit "disappeared", check which of the two you actually did — a saved look never enters the public pool.

Can other players see your saved outfits?

Not documented anywhere (to be verified). What is known: published outfits are public by design — they appear in the community browser with your code attached. Saves behave like a private wardrobe, but no source confirms whether other players can view your saves through your profile. If privacy matters, the safe assumption is the same one for any Roblox game: publish only what you are comfortable being public.

Why outfits fail to save (and the fixes)

Community documentation points at one specific quirk plus the usual sync suspects:

1. The unnamed-save quirk. Saved avatars reportedly fail to load — or fail to save cleanly — when they are given a name; leaving the save unnamed is the documented workaround. If your named save is acting up, re-create it unnamed before assuming data loss (single community source, to be verified).
2. Sync delays. A save that "didn't happen" right after equipping sometimes just lags — rejoin and check the wardrobe before re-doing the look (see the items not loading guide for the rejoin checklist).
3. Storage ceiling. Community trivia documents a save capacity around 4,000 outfits (to be verified) — practically unreachable, but worth knowing it exists.
4. The purchase-adjacent confusion. Buying items does not save your current look automatically — saving is a separate action. If you expected a look to persist after buying, save it explicitly.

FAQ

Where are my saved outfits stored?

In your in-game wardrobe inside Catalog Avatar Creator. They are not Roblox inventory items — inventory holds purchases, the wardrobe holds looks (see how to play for the split).

Can I move a saved outfit to another account?

No documented transfer exists (to be verified). The closest bridge is the outfit code: publish the look (or load-and-republish it on the other account) and share the code.

My save loads but items are missing — which guide do I need?

That is the display-side failure, not a save failure: work through the clothes not showing checklist, which covers editor-vs-inventory confusion and per-item fixes.

Related

• Clothes not showing — the number one fix guide
• Outfit codes — the public side of saving
• How to play — the full loop
• Items not loading — the rejoin checklist