How to read the result
The large number is the uncompressed estimate, in megabytes, using 1,048,576 bytes as one megabyte. That is the same unit as the server limit. 8,388,608 divided by 1,048,576 is exactly 8. A result of 0.25 MB is about a quarter of one of those megabytes. A result of 34.33 MB is more than four times the upload limit if you were sending the pixels with no compression at all.
You are not sending pixels with no compression when the file is a JPEG or a WebP. Those formats throw away or rearrange data so the file on disk is smaller than width times height times three. The large number is a ceiling for an uncompressed RGB image, not a prediction of your export. If the uncompressed figure is under 8 MB, a JPEG of those same pixels will also be under 8 MB, because compression does not make the file larger than the raw pixels in any case you will meet here. If the uncompressed figure is over 8 MB, the JPEG might still fit, or it might not. Only the file size on disk can answer that.
That is what the optional field is for. Type the size your computer shows, in megabytes, and the calculator multiplies by 1,048,576 and compares the result with 8,388,608. A file of 7.5 in that field is under the limit. A file of 8.1 is over it. Leave the field blank when you only know the pixels. The page will not invent a compressed size.
RGB uses 3 bytes for each pixel: one for red, one for green, one for blue. RGBA uses 4, with an extra byte for opacity. A clothing flat lay on a solid background is usually RGB. A PNG that kept a transparent background is the case for 4. FashionUGC does not require transparency. A transparent PNG is still just a file that must be under the byte limit and must show the garment. The channel chip changes only the uncompressed estimate.
The sentence under the number repeats the pixel count and the byte count so you can paste them into a brief. It does not say the video will be sharper because the still was heavier. Sharpness is whether a person can see the cloth. The byte count is whether the server will accept the file.
The limit, in bytes
The create form accepts JPEG, PNG, and WebP, up to six files, each no larger than 8,388,608 bytes. That number is 8 times 1024 times 1024. It is the default checked in the upload guard. People say “8 MB” for it. A round 8,000,000 bytes is a different, slightly smaller count. This calculator uses 8,388,608 so a file that would pass a decimal megabyte test and fail the server, or the reverse, is not mislabeled.
The limit is per file. Six photographs at 8,388,608 bytes each would be 50,331,648 bytes together. That total is arithmetic, not a second rule. The form checks each file. One 9 MB file fails even if the other five are tiny. Six acceptable files can still be the wrong upload if they are two garments, or two colours of the same style. One job is one garment and one colour. The product photo guide is the longer account of which stills are useful. This page is only the size.
A file over the limit is refused. Making it smaller is your export step, in the camera app or an editor, before you drop it on the form. This calculator does not resize, recompress, or strip metadata. It will not open the photo. If you need the real byte count, read it from the file properties and type it in. Do not type the uncompressed estimate into the file-size field and then treat that as a JPEG.
Formats outside JPEG, PNG, and WebP are not what the form lists. A phone that saves HEIC needs a conversion to JPEG or PNG before the size check means anything for this upload. A GIF is not on the list either. A BMP can be close to the uncompressed figure and fail the limit while a JPEG of the same pixels would pass. Convert first, then measure the file you will actually send.
MDN’s guide to image file types is a plain account of how JPEG, PNG, and WebP differ. JPEG is built for photographs and is lossy. PNG is often larger because it is built to keep every pixel, including transparency. WebP can be either lossy or lossless. FashionUGC accepts all three. It does not prefer one of them for “better video.” A readable garment in a small JPEG can beat a heavy PNG of a blurry garment.
Worked pixel sizes
The bronze gown source still published on this site is 236 pixels wide and 376 tall. Uncompressed RGB is 236 times 376 times 3, which is 266,208 bytes, about 0.25 MB. The JPEG on disk is 14,568 bytes, about 0.01 MB. Both are far under 8,388,608. The JPEG is about eighteen times smaller than the uncompressed figure. That gap is the whole lesson of the calculator. If you only had the pixels, you would know the file cannot exceed a quarter of a megabyte once compressed in any ordinary way, and you would still not know the 14,568-byte count until you looked at the file.
The floral dress source still is 429 by 715. Uncompressed RGB is 429 times 715 times 3, which is 920,205 bytes, about 0.88 MB. The JPEG is 46,862 bytes, about 0.04 MB. Again the formula overshoots the file, and again both numbers sit under the cap. These stills are small on purpose as published examples. They are not a resolution to copy. A catalog photograph should be sharp enough to see the garment. It does not need to be 236 pixels wide.
A generated frame at 720 by 1280 is a different rectangle from those sources. Uncompressed RGB is 720 times 1280 times 3, which is 2,764,800 bytes, about 2.64 MB. The published JPEGs of those frames are much smaller: 53,844 bytes and 57,294 bytes for two bronze frames, and 106,478 bytes and 102,760 bytes for two floral frames. All of them would upload. None of them is the file you upload. You upload the photographs. The frames are what the video produced. The calculator is for the photographs.
1080 by 1920, uncompressed RGB, is 1080 times 1920 times 3, which is 6,220,800 bytes, about 5.93 MB. That estimate is under 8 MB, so a JPEG or WebP at those pixels will also be under the limit. It is a phone-shaped still, not a requirement. The aspect ratio calculator is where 1080 by 1920 becomes 9:16. File size does not tell you the ratio, and the ratio does not tell you the file size.
3000 by 4000 uncompressed RGB is 36,000,000 bytes, about 34.33 MB. That is over 8 MB as raw pixels and says nothing final about a JPEG. A careful JPEG of a 12-megapixel photo is often a few megabytes. A PNG of the same pixels, or a JPEG saved at a very high quality with a lot of fine pattern, can land over the cap. Type the real file size. If it is 6.2, it passes. If it is 11, it does not, and you compress or scale before upload.
4000 by 6000 uncompressed RGB is 72,000,000 bytes, about 68.66 MB. RGBA at 4 bytes instead of 3 is larger by a third: the same pixels are about 91.55 MB uncompressed. A phone original in that range is a normal reason to export a JPEG and check the new file. Do not upload the uncompressed estimate. Do not assume every 24-megapixel JPEG fails. Measure it.
The same 3000 by 4000 picture with a typed file size of 7.5 MB is 7,864,320 bytes, under 8,388,608, with a little room to spare. At 8.0 in the field the calculator treats the number as 8 times 1,048,576, which is exactly the limit, so it passes. At 8.01 it is over. That edge is why the byte count matters more than a rounded “about 8 MB” in a file dialog. If your computer shows 8.0 MB and the upload is refused, look at the exact byte count. The server is counting bytes.
What compression changes, and what it does not
A JPEG decides which detail to keep. Smooth cloth compresses more than a dense floral print or a noisy background. Two photographs with the same pixel dimensions can differ by several megabytes. The calculator cannot see the print. web.dev’s learn images material is a clear walk through why a photograph and a graphic do not compress the same way. Use it if you are choosing an export setting. Then come back and type the size of the file you exported.
PNG keeps pixels. A photograph saved as PNG is often several times the JPEG of the same picture, sometimes large enough to cross 8,388,608 bytes while the JPEG would not. If the only reason for PNG was habit, export JPEG or WebP and check again. If you need PNG because of a cut-out background, check the file size after the cut-out. Transparency does not shrink the garment.
WebP can land smaller than JPEG at a similar look, or not, depending on the encoder. Acceptance on the form is not a quality ranking. A WebP that is 1 MB and sharp is fine. A WebP that is 1 MB and smeared is not a better source than a 3 MB JPEG you can actually see. Google’s image guidelines ask for a clear picture of the thing the nearby text names. The upload limit does not replace that. A clear picture that is over the limit still has to be made smaller without turning the cloth into mush.
Metadata, a colour profile, and an embedded thumbnail add a little to the file. They rarely explain a jump from 2 MB to 12 MB. The pixels and the quality slider explain that jump. Stripping a profile to win a few kilobytes is optional. Crossing from 9 MB to 7 MB usually means a lower JPEG quality or a smaller pixel dimension, not a metadata cleanup.
Scaling and compressing are different. A 4000 by 6000 image scaled to 2000 by 3000 has one quarter of the pixels, so the uncompressed figure drops by about four times, and the JPEG usually drops as well. The garment has to stay readable after the scale. If you can no longer see the stitch you meant the video to show, the file is small enough and the still is worse. Stop at the smallest file that is still a true picture of the piece, and confirm it is under 8,388,608 bytes.
Six files, one garment
The form allows up to six images. Front, back, side, detail, on-body, and flat lay are useful kinds of reference when you have them. They are not a required set. One sharp photograph can be enough. Six blurry crops of the same front are not six angles. The size calculator will pass each of them if each file is under the limit. Passing is not the same as being a useful set.
If every file is 7 MB, the six together are 42 MB. That is six times 7, times 1,048,576 bytes. The server still judges them one by one. A slow connection is your problem to plan for, not a different published cap. Do not split one garment into a second job because the total felt large, and do not combine two colours into one job because each file was small.
A detail crop can be a small file and a large help, if the crop is the print, the clasp, or the stitch of the same piece. A detail of a different garment, or a label from a different colourway, is a small file and a bad upload. The byte count will not catch the mix-up. You will see it when the video blends two products, and by then you have spent the generation.
Flat lays follow the same limit. An overhead photograph of one piece is one file, JPEG or PNG or WebP, under 8,388,608 bytes. The flat lay guide is about when that overhead view is enough. This calculator does not know whether the flat lay includes a second item in the corner. Crop the second item out before you worry about the megabytes.
On-body and packshot photographs of the same colour can share a job. They still cannot share it with a second size if you are trying to sneak a different fit into the same video. The file size of the on-body JPEG is irrelevant to that rule. Keep the set honest, then check each file against 8,388,608 bytes.
The published files, counted
These six pictures are the two published generations and the stills they came from. The source JPEGs and the frame JPEGs are all far under the upload limit. The captions use the byte counts of the files on this site. They are examples of the gap between pixels and disk size. They are not a recommended export setting, and they are not a claim about video bitrate. FashionUGC does not publish a bitrate or a guaranteed pixel size for the MP4.
Put 236 and 376 into the calculator with RGB selected. You should see about 0.25 MB uncompressed, and 266,208 bytes. That is the ceiling, not the 14,568-byte JPEG. Put 429 and 715 in and you should see about 0.88 MB uncompressed against a 46,862-byte file. Put 720 and 1280 in and you should see about 2.64 MB uncompressed. The frame JPEGs sit between about 53,000 and 107,000 bytes. If your result disagrees by more than rounding, you have a different channel chip selected, or a file size typed into the third field that the sentence is judging separately.
None of these files was refused for size. A refusal would have meant a different still. The gown frames also show a mannequin source becoming a worn picture. A heavier JPEG would not have promised a more faithful neckline. When you review a generation, look at the cloth. The calculator’s job ended when the upload was accepted.
Merchant listings care about the picture of the product you are selling. Google’s image link requirements are about that picture in a product feed, not about the FashionUGC upload cap. A file can be under 8 MB and still be a poor listing image if it hides the garment. A file can be a perfect listing image and still need a smaller export before this form will take it. The two checks are sequential. Size first, so the upload works. Truth of the picture second, so the video and the product page match.
What a large file does not buy
A 7 MB photograph is not a better brief than a 1 MB photograph of the same sharp garment. The model does not receive a score for file weight. It receives the picture. Extra megabytes of fine noise, a heavy colour profile, or a dimension far beyond what the cloth needs are cost on the wire, not detail in the hem.
A tiny file can also be the wrong economy. The bronze example’s 14,568 bytes are enough to publish as a demonstration of that one still. They are not a studio delivery spec. If your 236-pixel-wide export has turned the weave into blocks, the file is small because the picture is small. Export larger until the cloth is clear, then stop when the file is still under the cap. There is a wide band between 15 KB and 8 MB. Most good clothing stills live in it.
Upscaling a small photo to 4000 pixels does not restore weave that was never captured. It raises the uncompressed estimate and sometimes the JPEG size, and the blur remains. The calculator will report the new pixel math honestly. It will not report a sharper dress. If the original is soft, reshoot or use a different frame from the set. Do not spend the byte budget on empty pixels.
Filters and heavy grain add file size and hide the product. A clean JPEG is often smaller and more useful. The photo guide says to skip blur and heavy filters. The size tool agrees only in this limited way: if a filter pushed you over 8,388,608 bytes, remove the filter before you crush the quality slider. You may find the file fits with the cloth intact.
Video length and photo size are different bills. A 30-second Astra file does not require a 30 MB photograph. A 10-second Piveth file does not require a 10 MB photograph. Prices are ₹149, ₹199, ₹279, ₹349, and ₹500 for the five sold lengths. You do not pay by the megabyte of the still. You pay for the length of the video. A refused upload costs a retry of the export, not a second price, if you have not started the job.
A practical check before you drop the files
Export JPEG, PNG, or WebP. Read the byte size or the megabyte size from the file, not from a preview window that rounded it. If you only have pixels, run them through the calculator so you know the uncompressed ceiling. If that ceiling is under 8 MB, you are safe on size for a normal compressed export. If it is over, export, then type the real size. Do not guess.
Repeat for each of the six or fewer files. Write down any file that fails. Fix that file. Do not rename it and hope. Do not zip the set. The form wants the images, not an archive. Do not put two garments in one frame to save a slot. The slot limit and the byte limit are both real, and breaking either one does not help the other.
Then look at the pictures at the size you will upload. Name the colour. Name the piece. If you cannot, the file is the wrong still even when the calculator says it fits. The product photo to video page is what happens after that check. The calculator stops at the bytes.
Mistakes this page is here to catch
The first mistake is treating the uncompressed number as the JPEG. A 34 MB raw figure for a 12-megapixel photo frightens people into destroying a good image. Export the JPEG and read the file. Many of those photographs are 2 to 6 MB and ready to upload.
The second mistake is the reverse. A dialog that says “about 8 MB” gets dropped on the form and is refused because the bytes are 8,400,000. Type the bytes if you have them, or use a megabyte figure with two decimals and remember the limit is 8,388,608 bytes, not 8,000,000.
The third mistake is HEIC. The camera roll size is not the JPEG size, and the format is not on the accepted list. Convert, then measure the converted file. The original HEIC byte count is not the upload.
The fourth mistake is six files of two products, each comfortably under 8 MB. The calculator will pass a size check it was asked to pass. It will not notice the second dress. Keep one colour in the set.
The fifth mistake is upscaling to feel professional. More pixels that were invented by a resampler are not more garment. They can push a PNG over the limit and still look soft. Scale down from a real capture, or keep the capture if it is already clear and under the cap.
The sixth mistake is using this page as a compressor or a resizer. It does not change the file. If the number says you are over, the next step is your editor, then a fresh reading of the new file. Refreshing the calculator with the same pixels will give the same uncompressed estimate. That is correct. The file size field is what should change after you export again.
The seventh mistake is a video-size confusion. This page does not estimate the MP4. It does not know a bitrate, and this site does not publish one. Duration and frame are the other two calculators. A 30-second 9:16 file is not “8 MB of video” because the photo limit is 8 MB. Those are different objects.
A short way to brief the files
List the stills you mean to upload, one line each: what angle, the pixel size, and the file size in bytes or megabytes. Run any uncertain line through the calculator. Mark pass or fix. Fix means a new export, then a new measurement, not a hope.
When every line passes, and every line is the same garment, upload. If the form refuses a file you marked as passing, believe the form and re-read the byte count. The calculator can be given a rounded number. The server sees the file. Keep the passing list with the job so the next colourway is photographed on purpose, not copied as a file size target from the last SKU.
