Publish and maintain an asset listing
Prepare previews, licenses, and deliverables, then choose how buyers will pay and receive the work.
Open Sell an asset when you have work ready to offer. Prepare both the public listing and the files or links a buyer will actually receive.
Explain what is included
Give the asset a clear title, description, and relevant category. Use previews that show its actual state. Mention required software, dependencies, setup work, or limits a buyer needs to know before choosing it.
Offer at least one license. Give each tier its own price or mark it free, and explain the permitted use. Only offer work and rights you are entitled to provide.
Add the deliverables
A listing can include uploaded files or delivery links, with up to 12 deliverables. Each uploaded asset file can be up to 512 MB.
You can restrict an item to specific license tiers. For example, a source project can belong to a different tier from an exported model. Check those assignments before publishing; a paid tier should not promise a file gated to a different tier.
Public preview media and private deliverables are separate. Uploading a screenshot does not provide the buyer with the asset itself.
Choose payment and delivery
For supported onsite purchases, a completed payment grants the buyer library access for the license they bought. Finish the relevant seller and payout setup before relying on paid sales.
For a direct arrangement, agree on payment and handover with the buyer through the deal. This includes Robux arrangements. The direct path does not automatically grant library access.
You can save a draft while preparing the listing. A draft is not available to buyers until published.
Maintain the listing
Use Selling to edit, publish, or take a listing off the shelf. Keep the description and deliverables consistent when updating the work, and explain changes that affect how it is used.
Delisting stops new discovery and purchases but does not revoke an existing buyer's library access. Removing deliverables can affect those buyers, so check what they still need before changing the handover.
For a purchase problem, use the refund and support flow with the original transaction.