Your UGC item's thumbnail: the camera is chosen before publishing, and only once
The default thumbnail may not represent the item well, and there is an official plugin for framing the camera. The expensive detail: once the asset is uploaded, the thumbnail never changes.
Produced with AI from the sources cited below, and checked by automated verification against those same sources. No person read this text before publication. Editorial Policy
The thumbnail is the first thing anybody sees of your item — on the Marketplace storefront, in the inventory and in the avatar editor. And it has a property that changes how you should treat it: after the asset is uploaded, it does not change.
This guide covers how to control that framing before upload, and the two defects the documentation names with a known fix.
The problem
The thumbnail gives the preview of the 3D asset in three places: the Marketplace, the user's inventory and the avatar editors. It is not a storefront detail — it is the item's representation everywhere it appears without being worn.
You can create your own and control the preview's look exactly. The documentation classifies the step as optional, but explains why it is worth it: the default thumbnail may not correctly represent the item, and a custom thumbnail creates a more accurate preview.
In practice, "may not correctly represent" means concrete things: the item cropped, or tiny in the middle of an empty frame, or seen from an angle that hides precisely what is beautiful about it. The default camera does not know which side of your accessory is the front.
And here is the sentence that defines the urgency: the thumbnail has to be created before publishing the asset. Combined with the fact that it does not change after upload, the result is clear — there is no "I will adjust it later". Getting the thumbnail wrong means resubmitting the whole item, with a new fee.
Step by step
1. Install the plugin. The Custom Thumbnail Tool is the official route, and installing it may require restarting Studio.
2. Select the accessory in the Explorer.
3. Open the tool. With the accessory selected, go to the Plugins tab and click the UGC Thumbnail Tool. The viewport updates and centres on the accessory.
4. Frame it. There are four controls, and the fourth is what makes the difference to the result:
- W A S D pans the camera.
- Right button held orbits the camera.
- Middle button held also pans.
- Shift held gives fine adjustment.
Fine adjustment is what separates a decent thumbnail from a good one. Framing a small item is sensitive to a few pixels, and without Shift the camera moves in steps that are too large.
5. Confirm. The Accept button generates the thumbnail configuration objects.
It is worth knowing what it creates, because that makes the state inspectable: the information sits in a ThumbnailConfiguration object, a child of the accessory, which in turn has a CameraTarget and a CameraValue. If those objects disappear, the thumbnail goes back to the default — and it is good to know that before tidying the hierarchy.
6. Check before uploading. Right-clicking the accessory and choosing to save to Roblox, the asset configuration window appears showing the current thumbnail. If it is not good, redo the framing and overwrite.
This step is the only moment where you can see the real result before it becomes permanent. Skipping this check is a gamble.
A note on what the thumbnail has to show. The framing is not a pretty photo of the item — it is the information the buyer uses to decide. Three things compete for the frame: the silhouette, which says what the item is; the detail, which says whether it is well made; and the scale, which says how it will look on the avatar.
No angle delivers all three with the same weight, and that is where the decision happens. An item with a strong silhouette — a hat with an unusual shape, a large backpack — gains more from an angle that shows the outline. An item whose value is in the texture gains more from a close-up. And a small item, like a face accessory, almost always needs more zoom than the default camera gives, because on the storefront it is going to appear small again.
The honest test is looking at the thumbnail at the size it actually appears — reduced, in a grid with others. Framing that only works full screen does not work.
The artifact
The document below is the script in checklist form, with a prerequisites section that comes before opening the tool — because the two known defects are not fixed by framing the camera.
At the end of it is the table of the two defects, with symptom, cause and fix. It exists because both share a characteristic that makes them hard to find, and that is the subject of the next section.
One further care about the hierarchy. The three objects holding the framing live inside the accessory, and any operation that rebuilds the item — recreating the Accessory, pasting an old version, reimporting the mesh over it — can take them away. Since the thumbnail silently reverts to the default in that case, the check through the configuration window is what catches it.
And there is a detail of order that saves a round: check the thumbnail after every change to the Handle. Since the framing's scale depends on it, a size adjustment made after accepting the camera changes the result with nothing warning you.
Common mistakes
Wrong zoom. The item appears cropped, or tiny. The cause is not the camera: the thumbnail's scale depends on the size of the accessory's Handle. For the best thumbnail, the Handle has to cover the whole item.
It is a dependency nobody guesses. The Handle is the accessory's functional part, and it is common to leave it small — it does not need to be large for the item to work. Except the thumbnail system uses its size to decide the framing.
And the fix comes with a specific warning: when changing the Handle's size, adjust the Size property, and not Studio's scale tool. The reason is written down — the scale tool can cause other unintended changes to the item. It touches more than the size.
A backwards thumbnail. The item appears turned around. The cause: when importing a mesh, Studio can change the model's orientation by 180 degrees. The fix is rotating the mesh 180 degrees in the modelling program and reimporting.
And here is the characteristic the two defects share, and which makes them treacherous: regardless of the import orientation, Studio equips the accessory on the character with the same fit and attachment.
Meaning: the item wears correctly. You test it on the avatar, spin the character, look from every side, it is perfect. The defect exists only in the thumbnail — and the thumbnail is the one thing you did not check, because it looked like an automatic consequence of the model.
That is why step 6 of the script is not optional. It is the only place where both defects appear before it is too late.
Treating it as genuinely optional. The documentation calls the step optional, and that is about requirement, not about value. The default thumbnail exists and works; it just does not know which side of your item is the front or what in it deserves emphasis. In a catalogue where the buyer decides from the image, that is not a detail.
Trusting the wearing test. It is the mistake that encompasses the previous two and deserves saying on its own: testing the accessory on the avatar does not test the thumbnail. They are two independent paths inside Studio, and the item can be perfect in one and wrong in the other. Anyone who finishes the work by wearing the item on the character, liking it and uploading, has never looked at the thumbnail — and it is the one irreversible part.
Next step
The order that saves money is simple and goes against instinct: frame the thumbnail before considering the item finished, not afterwards.
In practice, that means opening the tool as soon as the accessory is assembled in Studio — before texturing the last detail, before writing the description. If the framing reveals the Handle is wrong or the model is backwards, you find out while it is still cheap to fix.
After that, it is worth keeping the framing as part of the item's file. The ThumbnailConfiguration, CameraTarget and CameraValue objects live inside the accessory — so saving the Studio file preserves the camera. For a collection of similar items, that lets you reuse the same angle, which gives the whole storefront visual consistency.
And keep the rule that sums it all up: the thumbnail is the one part of the item you cannot fix later. Everything else — description, price, availability — can be fixed. It cannot.
Sources
Ready-to-use artifact
CUSTOM THUMBNAIL FOR A UGC ITEM. Checked on 23/09/2026.
!! THE THUMBNAIL DOES NOT CHANGE AFTER UPLOAD. It has to be right BEFORE
publishing the asset. Got it wrong? the whole item has to be
resubmitted, with a new fee.
== BEFORE OPENING THE TOOL ==
[ ] does the HANDLE cover the whole item?
the thumbnail's scale depends on the Handle's size. A Handle
that is too small = a cropped item; too large = a tiny item in
the middle of nothing.
[ ] when adjusting the Handle, did you use the SIZE property?
do NOT use Studio's scale tool: it can cause other UNINTENDED
changes to the item.
[ ] is the model facing forwards?
when importing a mesh, Studio can flip the model 180 degrees.
== THE SCRIPT ==
[ ] install the Custom Thumbnail Tool plugin
(it may require RESTARTING Studio)
[ ] select the Accessory in the Explorer
[ ] Plugins tab > UGC Thumbnail Tool
the viewport updates and centres on the accessory
[ ] frame the camera:
W A S D ............ pan
RIGHT button ....... orbit
MIDDLE button ...... pan
SHIFT .............. fine adjustment
[ ] Accept
generates the configuration objects
[ ] CHECK: right-click the accessory > Save To Roblox...
the configuration window appears showing the CURRENT thumbnail.
Not happy? redo the framing and overwrite.
== WHAT GETS SAVED ==
Accessory
└── ThumbnailConfiguration
├── CameraTarget
└── CameraValue
Those two are what hold the framing. If they disappear, the thumbnail
goes back to the default.
== THE TWO KNOWN DEFECTS ==
| Symptom | Cause | Fix |
|--------------------------|--------------------------|------------------------------|
| wrong zoom, item | the Handle does not | adjust the Handle through |
| cropped or small | cover the whole item | the Size property |
| item facing BACKWARDS | Studio flipped the model | rotate the mesh 180 degrees |
| | 180 degrees on import | in the modelling program and |
| | | reimport |
In both cases the accessory still equips CORRECTLY on the character --
Studio uses the same fit and attachment regardless of the import
orientation. That is why the defect only shows in the THUMBNAIL, and
why it goes unnoticed by anyone who tests by wearing it.
