Start with the file, not repeated submissions
When a Roblox shirt is not uploading, repeated attempts rarely identify the cause. Separate the problem into three stages: whether the browser selected a valid image, whether the artwork matches the Classic Shirt format, and whether the current Roblox creation flow accepted the submission. The local size checker above handles the first technical step without sending the image anywhere.
Select the exact file you intend to submit and read its decoded width, height, format, and file size. Do not rely on the dimensions shown in a design document or a filename such as “shirt-585x559-final.” The pixels decoded by the browser are the evidence that matters.
Confirm that you made a Classic Shirt
A Classic Shirt wraps artwork around the torso and arms. Its working canvas is different from a square Classic T-shirt image and different again from Layered Clothing. A complete Classic Shirt template uses a 585×559 canvas. A square logo image belongs to a Classic T-shirt workflow and cannot become a wrapped Shirt merely by renaming it.
If the source is not 585×559, first ask whether the wrong clothing type was selected. Resizing an arbitrary square logo to 585×559 stretches the image but does not create the required body-face mapping. Return to a blank Shirt template and place the artwork on the intended front, back, side, top, and bottom regions.
Verify the real image format
Use a genuine PNG export for predictable hard edges and transparency. A file extension is only a label. Renaming design.jpg to design.png does not convert the encoded image. The checker reads the decoded type so you can spot that mismatch.
JPG removes normal alpha support and may add compression artifacts around text and edges. WebP can be decoded locally by modern browsers, but a conservative upload workflow should use a freshly exported PNG when the platform flow expects common image input. Reopen the PNG after export and make sure it is not empty, corrupted, or an editor project file with the wrong extension.
Inspect transparency and visible coverage
A technically decodable image can still be unusable. An entirely transparent file has no visible clothing. A nearly empty template may contain only guide marks. A fully opaque background may cover regions that were intended to remain transparent.
Run the full clothing checker after the size check. It reports visible pixels, transparent pixels, partial alpha, mapped UV coverage, and pixels outside expected clothing regions. These signals cannot guarantee acceptance, but they reveal common export mistakes before another submission.
Template guide labels should not appear in the final design unless they are intentionally part of the artwork. Export a clean copy, keep the editable master separately, and inspect the result against light and dark backgrounds.
Do not upload a screenshot of the editor
Screenshots often include toolbars, margins, zoom scaling, and operating-system pixels. Even when a screenshot happens to be 585×559, its content is not necessarily aligned to the Shirt UV regions. Export the artwork from the canvas instead.
If you only have a screenshot, move the intended design into a clean first-party template and rebuild the mapping. Cropping and resizing the screenshot can hide interface chrome, but it cannot infer which image areas should wrap around each body face.
Check the creation flow and account context
After the local file passes technical checks, confirm that you are using the current official Roblox creation interface and the correct clothing category. Platform navigation, eligibility, fees, permissions, group ownership, and publishing steps may change. SkinEditor.org does not inspect your account and cannot confirm account-specific requirements.
Make sure the intended creator or group is selected before submission. If the form reports a specific account, permission, or payment message, treat that message as a separate issue from image dimensions. Do not alter a valid image to solve an account permission error.
Rule out a temporary browser problem
Refresh the official creation page, then select the file again. If the chooser appears to do nothing, verify that the file still exists and can be opened locally. Try a current browser with extensions temporarily disabled, especially extensions that block scripts, cookies, popups, or uploads.
Avoid repeatedly clicking the submission control while a request is pending. A private browsing window can help distinguish cached browser state from a file problem, but it may also require signing in again. Never enter Roblox credentials into this site; the diagnostic tools here do not request them.
Read the exact error message
“Not uploading” can describe several different failures: the chooser rejects the file, the preview never appears, the submit button stays disabled, a network request fails, moderation rejects the asset, or the asset submits but does not become usable. Record the exact wording and the stage where it happens.
A dimension or decode error points back to the source file. A permission message points to account context. A moderation message belongs to content and rights review. A temporary server message may resolve without changing the image. Keeping those categories separate prevents unnecessary edits.
Use a controlled retry
Create one clean test file from a blank Shirt template. Add a small piece of original, non-sensitive artwork to the mapped torso region, export as PNG at exactly 585×559, and run both local checks. Submit that file once through the official flow.
If the clean test works, compare it with the failing file: encoded format, alpha, dimensions, guide residue, complexity, and content. If both fail at the same account or network stage, the image is less likely to be the cause. This A/B test is more useful than making many unrelated changes at once.
Rights and moderation remain separate
Passing technical checks does not mean an asset will pass moderation. Logos, copied clothing, celebrity likenesses, protected characters, misleading marks, sexual content, hate symbols, and other restricted material can create rights or policy problems. Only submit artwork you created or have permission to use.
Do not attempt to disguise prohibited content or evade moderation. If the platform supplies an appeal or review process, follow the current official instructions and provide accurate ownership information.
Privacy and scope
The size checker decodes the selected image in your browser. Pixels, filenames, and results are not uploaded to SkinEditor.org, and no account or database record is created. Closing or refreshing the page clears the temporary result.
This page provides a technical checklist, not a guarantee that Roblox will accept an asset. Roblox publishing behavior and requirements can change. SkinEditor.org is independent and is not affiliated with Roblox Corporation.
Continue with the moderation failure checklist when the file submits but is rejected, or use the display and seam guide when an accepted Shirt maps incorrectly.
Frequently asked questions
What size should a Roblox Classic Shirt be?
A full Classic Shirt template uses a 585×559 canvas. A square image is generally associated with a Classic T-shirt workflow, not a wrapped Shirt.
Can I fix the upload by renaming JPG to PNG?
No. Renaming does not change the encoded image. Export a real PNG from the source editor.
Does a passing local check guarantee upload success?
No. It verifies local technical evidence only. Account permissions, platform availability, content policy, rights, and moderation remain separate.
Is my shirt sent to this website?
No. The checker reads dimensions and preview data locally in the browser.