My first outfit game. A lot of copying and pasting.
I was building my first outfit try-on game on Roblox. I wanted to feature outfits made by the community in games like Catalog Avatar Creator (CAC) and Avatar Studio by Envy. Finding outfits was the fun part. Getting them into Studio was another story.
I searched for each item by name on the Roblox Marketplace website, copied its asset ID, and organized those IDs into lists by asset type and outfit. Then I used those lists to rebuild the outfits on avatar rigs. Every outfit meant doing it all over again.
Looking back, I still wonder why I put myself through that. I kept hoping I’d find an easier, quicker way, but I couldn’t find one that worked for what I needed.
A couple of friends even helped me collect and organize everything in their free time. I couldn’t afford to pay them back then, and they still showed up for me. They were real ones, and I haven’t forgotten it.
That work eventually paid off: the same game went on to reach more than 1.5 million visits and earn over 13 million Robux. I’m proud of that, but I also remember how much repetitive work it took just to get started.
I wasn’t the only one doing it the hard way.
I kept seeing other creators ask for the same thing: a straightforward way to bring outfits into Roblox Studio. Many were collecting item IDs just like I had. Others were buying the items so they could save the outfits to their Roblox account before bringing them into their projects.
For me, buying an entire outfit just to recreate it in Studio felt like an expensive workaround. Creators were already putting time into their games, animations, and graphics. I wanted importing an outfit to be a much smaller part of that work.
Bringing CAC importing to Bloxiana.
In August 2025, I started working on an unofficial way to bring CAC outfits into Roblox Studio through commands in Bloxiana, my general-purpose Roblox Discord bot. I released its CAC importing feature publicly on August 20, and it quickly gained traction.
CAC’s owner even reached out to ask how I’d made it work. From our conversation, my impression was that he was okay with it at the time. Later, fetching outfit data through codes became subject to rate limits, and users of Bloxiana’s CAC features could experience delays or requests being rate-limited.
People clearly wanted the feature. Keeping it dependable was the harder part.
A useful workaround still has its limits.
I saw other developers explore similar ideas, though I can’t speak for why individual projects slowed down or stopped. From my own experience, maintaining an unofficial integration takes ongoing work and resources to keep it available around the clock.
I had access to resources that helped me keep Bloxiana’s CAC features running. Even so, that didn’t change the underlying problem: an unofficial method can change or stop working, and its future is outside your control.
I also saw importing tools presented as exploit scripts. That wasn’t a direction I wanted creators to have to rely on. Bringing an outfit into Studio should be a normal part of creating, without asking someone to run an executor.
I wanted exporting to be part of the game itself.
I wished catalog games, including CAC, would offer exporting directly in-game. I can’t speak for their decisions. Infrastructure costs, abuse prevention, ongoing maintenance, and whether a paid feature could support those costs are all considerations I’ve had to think about myself.
As a creator waiting for that feature, though, it was frustrating. It sometimes felt like the community’s need for an easier workflow wasn’t being prioritized. I wanted to build something where it was.
That’s why I made mewsy. With our own catalog game and Studio plugin, exporting can be a feature we build and maintain directly, using outfit data from our own game.
The tool I wish I’d had in 2023.
In 🛍️ mewsy outfit catalog, pair the plugin using the /studio command. Send your currently worn avatar, or select multiple saved outfits and choose Export to Studio. Spend your time building your outfit game, animating a character, or creating a render instead of collecting IDs.
In-game exports to Studio are always free, with no paid unlocks or monthly export allowance. Busy periods may bring delays or temporary usage restrictions, because keeping the service available still takes resources.
For developers who want outfit data outside our game, a separate developer API is coming November 2026. That’s for your own tools, catalog experiences, and avatar customization features. You don’t need it for the free in-game export flow.
The kitty mascot and a little mischief give mewsy its personality. The reason it exists is simpler: I remember how much work this used to take, and I want the next creator building their first game to have an easier start.