A product's Media page has two parts: Media, for the images and video on the product page, and Files and versions, for what owners download. You need the Edit products permission. Deleting a file version also needs Delete products.
To get there: in your store's dashboard, open Products, pick the product, then open Media.
Images and video
Add an image
Press Upload image and pick a file.
PNG, JPEG, WebP, GIF or AVIF, up to 25 MB.
Enviglo keeps images at full quality, up to 3840 pixels across (4K). Anything larger is shrunk to fit. Images are saved as WebP without losing any detail.
Animated GIFs keep moving.
What a product image has to be
Every image on a product has to meet two rules. An image that doesn't is turned away when you add it, and the message says which rule it broke.
At least 1280 × 720 pixels. Upload the original, not a thumbnail.
Landscape, between 4:3 and 21:9. Cards and the gallery show images in a wide frame, so square icons, portrait shots and very tall screenshots can't be used. 16:9 (like 1920 × 1080) and 16:10 fit best.
Videos and YouTube links don't have to meet these rules.
Keep images sharp, too. Enviglo's team looks at every image when it reviews the product, and an image enlarged from a smaller one is blurry however many pixels it has, so it may be turned down. Take a bigger screenshot or render instead of scaling a small one up.
Add a video
Video on a product page comes with Pro, whether you upload it or link it from YouTube. On Free neither control appears; a video already on a product stays where it is.
Press Upload video for an MP4, WebM or MOV file up to 200 MB.
Or paste a YouTube link into YouTube video and press Add video. Links to a video's watch page, youtu.be links, Shorts and embed links all work.
Videos play in the gallery on the product page.
Enviglo checks everything first
Every image and video you add is checked by the Enviglo team before it appears on the product, as part of the product's review.
While it waits, it shows under Waiting for review, marked Pending. Press its bin icon to take it back.
On a product that hasn't been approved yet, it's reviewed with the product: approving the product approves it too. Nobody at Enviglo sees it until you submit the product, so until then it shows under Not sent for review, marked Not sent. You can submit the product while its only image is waiting. See Submit it for review.
On a product Enviglo has approved, it's one of the product's changes, and goes to the team with any new name, description or file waiting. Approving the changes approves it. See Changes to an approved product.
Once it's approved, it's added to the end of your media.
If the team turns down the product or its changes, your images and videos keep waiting with it, and go to the team again when you send it again.
If an image or video itself is rejected, it never shows publicly and a line under Media says why. The person who uploaded it is told, and so is everyone on your team who gets notified about A decision from Enviglo. It's also listed on your store's Notices page. See Notices from Enviglo.
An upload only counts towards publishing once it's approved.
How many you can add
A product can have 12 media items, counting ones still waiting for review. The counter shows how many you've used, for example 3/12. At 12, the add buttons are greyed out until you remove something.
Order and cover
Drag a tile by its handle to move it. The keyboard works too. To remove one, press the bin icon on its tile.
Your first image is marked Cover, wherever it sits among your videos.
Cards in browse, search and on your storefront use your first image as the cover, and show your second image when someone hovers. For both to work, keep images in the first two places.
The product page's gallery shows everything in your order, starting with the first item.
Cards and the gallery use a wide frame (16 by 10) and crop images to fill it, so keep the important part near the middle.
Publishing needs at least one image, and every image on the product has to meet the rules above. Images from before the rules came in, including those brought over from myPod (which arrived as Roblox's small thumbnails, not your originals), are marked on Media with what's wrong (Square, Too small, and so on); hover the mark to read why. A product that's already live keeps them and stays live, but it can't be published again, or announced as a drop, until they're replaced. A drop that was already announced still opens on its date.
A live product always keeps at least one image. To replace your only image, add the new one first, then remove the old one once the new one is on the product. A new upload waits for review before it counts; one picked with Choose from approved goes up straight away.
A product that went live without an image, like many that came over from myPod, is shown with a cover Enviglo draws for it and sits behind products that have a picture of their own. Unless its description runs to a couple of sentences, search engines such as Google aren't asked to list it either. It's flagged No artwork, or Not in Google yet, under Needs attention.
Your in-game hub can't show images hosted on Enviglo. Set the picture it uses with In-game hub image on the Delivery page. See Delivery on Roblox and Discord.
Files and versions
This is what owners download from their library. A product needs at least one before it can be published, and a live product always keeps one.
Upload a version
Type a Version, such as 1.3.0.
Under What changed, write what's new, one change a line. This is optional, but it's what owners read.
Press the box that says Choose a file (.rbxm, .zip, .fbx, .unitypackage…) and pick your file.
Leave Tell owners about this version ticked to send owners a notice, or untick it for a small fix. See Tell owners about an update.
Press Upload version. A percentage shows while it uploads.
The rules:
Most types of file, up to 50 MB on Free, 250 MB on Pro and 2 GB on Ultimate. A Roblox model, script or plugin is usually far under that. Enviglo checks every upload first. See What Enviglo checks in a file.
The version can be up to 32 characters: letters, numbers, dots, dashes, underscores and plus signs, with no spaces. It must start with a letter, number or underscore.
Each version number can only be used once per product.
A product keeps up to 20 versions on Free, 50 on Pro and 100 on Ultimate. The counter shows how many you have, for example 4/20.
Numbers show with a "v" in front, so 1.3.0 appears as v1.3.0. A word like Beta shows as you typed it.
Notes can be up to 2,000 characters.
On a product Enviglo has approved, a new version goes to Enviglo's team first, marked Waiting for approval, and owners keep the version before it until it's approved. The box reads Tell owners once it's approved, and they're told then. See Changes to an approved product.
What Enviglo checks in a file
Every version is checked as it uploads, and so is every file inside a zip or Unity package. Nothing leaves Enviglo to be checked.
Enviglo won't accept a file that is, or contains:
A program or installer for Windows, Mac or Linux, such as an .exe, .msi, .bat, .dmg, .pkg or .apk, or a shortcut. It goes by what a file is, not its name, so renaming one doesn't get it through. Plugin libraries (.dll, .dylib, .so) are fine in Unity and Unreal products.
An archive Enviglo can't look inside: a password-protected zip, a .rar or a .7z. Upload a zip without a password instead.
A file that isn't what its name says, such as a .rbxm that isn't a Roblox model, or a zip that's damaged.
A zip bomb: a zip that says it unpacks to far more than any product needs.
A script Enviglo's moderators have already found harmful in another product, such as a known backdoor.
If a file is refused, the upload stops with the reason, and nothing is kept. Fix it and upload the version again. Scripts are fine: .lua, .luau, .py, .js and the rest are what products are made of.
Enviglo also reads the scripts in Roblox models and places for signs of a backdoor, like sending data to a Discord webhook or loading a hidden module. A file that shows one is still uploaded and stays available to buyers, and Enviglo's moderators take a look. Plenty of honest products load modules by their ID, so that alone doesn't count against yours. Files uploaded before these checks existed are being checked the same way.
If Enviglo flags a version
You get a notification, and the version shows what was found under Files and versions on the product's Media tab. Each finding names the scripts it's about by where they sit in your model, like Workspace.Car.Chassis, so you can find them. Nothing changes for your buyers while Enviglo's team looks, with one exception: a new version with code shaped like a backdoor, such as a script reaching require through getfenv, is Held for review. Your buyers keep getting the version before it until the team has looked. Once it's cleared, it goes out to them and you're told, and you can tell its owners about it. You can still download or delete a held version yourself.
Obfuscated code is fine. Protecting your scripts with Luraph, PSU or any other obfuscator never gets a version flagged or held on its own. The check also skips comments and text in strings, so a readme in a comment that mentions loadstring or require doesn't count. It reads what your scripts actually run.
If you know why the code is there, press Explain and say what it does, who wrote it and whether buyers need it. Most flags turn out to be honest code, like a webhook buyers fill in with their own server or an admin system's loader, and an explanation helps the team decide sooner. You can change what you said until they do. Once they've looked, the version says so.
If Enviglo refuses a script
When Enviglo's team finds a script is harmful, usually a backdoor that came in with a free model, every product carrying it goes Off sale until you upload a version without it. Meanwhile nobody can buy it and its owners can't download it, though they keep their licenses. If an older version of the product doesn't have the script, it keeps selling and owners get that version instead.
You get one notification and email for all of your products it affects. Each product's Media tab shows which script it is, and your store's Notices page lists every product that's off sale. Delete the script and upload a new version: once it passes the file check, the product goes back on sale by itself, and a draft stays a draft for you to publish. Uploads that still carry the script are refused.
It isn't a suspension or a warning, and it doesn't count against your store.
What owners get
The newest upload is marked Latest, whatever its number. That's the one owners download, from their library or from the Download button on the product page, which names the version.
The product page also lists the files under Included files. Once there's more than one version, or a version has notes, its Details tab shows a Version history with each version's notes.
Every new version shows as Updated in its owners' libraries until they download it, whether or not you tell them about it. If your store uses webhooks, they also get a File uploaded event, with the notes. See Webhooks.
Tell owners about an update
A notice goes to everyone who owns the product: a notification with your notes, and an email for people who get those. The email links to the version history, where the notes are in full. If your store posts its updates in Discord, the notice is posted in that channel too. See Post updates.
To keep notices worth reading:
You can send one notice for each version, and only for the newest one.
A product's owners get at most one notice a day. Until then the box is greyed out and says when you can send the next.
Each person gets at most two of these emails a day from all stores together. The rest still reach their notifications.
Owners can turn off these emails, and each email has a link to stop them.
To tell owners about a version you uploaded without a notice, press Tell owners beside it, then Tell owners again to confirm. It's only on the newest version, and only once a day's passed since the last notice.
To change a version's notes, press the pencil icon beside it, then Save notes. The version history shows the new notes. Anyone already told keeps the words they were sent.
Each version on your Media page shows how many times it's been downloaded and when it was last downloaded, or "Never downloaded". Your team can download any version from there.
Delete a version
Press the bin icon beside the version, then Delete. Owners can no longer download it, and you can't undo this. You need the Delete products permission.
You can't delete the only file of a product people own, because it's the only thing they can download. You also can't delete the last file of a live product. Upload the new version first, then delete the old one. A version held for review or waiting for approval doesn't count as a spare, since owners can't download it yet.
Troubleshooting
"Enviglo can't accept this file." Something in it is on the list in What Enviglo checks in a file, and the message says what and where. For a .rar or a zip with a password, zip the files again without one. For a program, take it out of the product.
"Use a PNG, JPEG, WebP, GIF or AVIF image." or "Images must be under 25 MB." Convert or shrink the image and try again.
"Use an MP4, WebM or MOV video." or "Videos must be under 200 MB." The same goes for videos.
"Products can have up to 12 media items, counting ones waiting for review." Remove an item, or take back an upload that's still pending.
"Paste a link to a YouTube video." The link isn't a YouTube video link. Copy it from the video's Share button.
"This image is square (420×420)…", "…too wide…" or "…must be at least 1280×720." The image breaks one of the rules for product images. Take a new screenshot or render at a bigger size, or crop it to a wide shape.
"Choose from approved" shows an image greyed out. It's already on your store, but it doesn't meet the rules for product images. Hover it to see why.
"Files must be under 50 MB." Split the download, make it smaller, or move up a plan: Pro raises the limit to 250 MB and Ultimate to 2 GB.
"Use a short version like 1.2.0." Take out spaces and other symbols.
"Version 1.3.0 already exists. Use a new version number." Every upload needs a new version number.
"A live product always keeps a file to download." Upload the new version first, then delete the old one. To take the product off the marketplace instead, unpublish it on Overview.
"Your plan keeps 20 versions of a product. Delete an old one first." Delete a version you no longer need, or move up a plan.
"Owners heard about an update less than a day ago." A product's owners get one notice a day at most. The version is uploaded all the same, and shows as Updated in their libraries.
"Only the newest version can be announced: there's a newer one now." Notices are only for the newest version. Tell owners about that one instead.
"You're uploading too quickly. Try again in a few minutes." One person can start 150 uploads an hour.
My image isn't on the product page. It's waiting for review with the product. Check Waiting for review on Media, and Status on Overview for the product's review.
My image has said Not sent for days. A new product's images are only reviewed with the product. Press Submit for review on Overview: you can send it while its only image is waiting.