How to read the result
The large number is the byte count of the media data at the rates you typed. Under it, the same count is shown as a decimal megabyte, meaning the bytes divided by 1,000,000, and as the kilobits per second you combined. Video rate and audio rate are added first. A silent file uses an audio rate of zero, so only the video rate remains.
If you fill the target field, a second sentence says what total kilobits per second would land on that many decimal megabytes in the seconds you chose. That sentence is the formula run backwards. It does not change the big number unless you then type the suggested rate into the video field yourself. The target is a budget you are testing. It is not a FashionUGC setting and not a marketplace rule.
The duration chips include the five lengths the create form sells, 10, 15, 20, 25 and 30 seconds, plus 60 seconds so you can see a minute that this product does not export. Sixty seconds in the calculator is only a size estimate. The length calculator is where a 60-second request is mapped back to the 30-second ceiling and its price. Do not read a 60-second size as a file you can generate here.
Rate chips of 1000, 2500, 5000 and 8000 kilobits per second are round numbers people type when they are planning. They are not measured outputs of Piveth or Astra. If your download is a different size, the encoder used a different average rate, or the container added a little, or both. Trust the file properties for that download. Trust this page for the arithmetic of a rate you are considering.
A container is the reason the last kilobyte is not sacred. MDN’s page on media containers describes the wrapper around the compressed picture and sound: an MP4 is that kind of wrapper. The formula here is the picture and the optional sound. Headers, an index, and a short time to start playback sit on top. For a ten-second clothing clip the wrapper is small next to the media data. For a one-second sting it can be a larger share. The estimate is a plan, not a byte-perfect promise.
The formula, written out
Kilobits per second times 1,000 is bits per second. Bits per second times the duration is the bits in the whole clip. Divide by 8 because a byte is 8 bits. That is the entire estimate. At 2,500 kilobits per second for 10 seconds, the bits per second are 2,500,000. Times 10 is 25,000,000 bits. Divided by 8 is 3,125,000 bytes, which is 3.125 decimal megabytes. The calculator should show that when those two fields are 10 and 2500 and audio is 0.
Five thousand kilobits per second for the same 10 seconds is twice the data: 6,250,000 bytes, or 6.25 decimal megabytes. Eight thousand for 10 seconds is 10,000,000 bytes, or 10 decimal megabytes. One thousand for 10 seconds is 1,250,000 bytes, or 1.25 decimal megabytes. Doubling the rate doubles the estimate. Doubling the seconds does the same. Thirty seconds at 2,500 kilobits per second is 9,375,000 bytes, or 9.375 decimal megabytes, three times the 10-second figure.
Audio adds before the division. A video rate of 2,500 plus an audio rate of 128 is 2,628 kilobits per second. For 10 seconds that is 3,285,000 bytes, or 3.285 decimal megabytes. The extra 160,000 bytes are the sound, not a sharper dress. FashionUGC does not put that sound in the file. If you add a track in an editor, the growth is about that large, plus whatever the editor’s wrapper does. Leave the audio field at 0 when you are estimating the silent download.
Run backwards, a target of 8 decimal megabytes in 10 seconds wants 6,400 kilobits per second total. Eight million bytes times 8 is 64 million bits. Divided by 10 seconds is 6,400,000 bits per second, which is 6,400 kilobits per second. If 128 of those kilobits are audio, the picture would have about 6,272. The calculator states the total when a target is filled. It does not subtract the audio for you, so you do not hide a soundtrack inside a picture rate by accident.
A target of 25 decimal megabytes in 30 seconds wants about 6,666.7 kilobits per second. Twenty-five million bytes times 8 is 200 million bits. Divided by 30 is about 6,666,667 bits per second. That is a planning rate for a length Astra can export. It is still not evidence that an Astra file will land on 25 megabytes. You will know the size when the file finishes, from the file itself.
Decimal megabytes and the 1,048,576-byte megabyte used on the photo file size calculator are not the same unit. 3,125,000 bytes is 3.125 decimal megabytes and about 2.98 of those larger megabytes. This page uses the decimal unit because video bitrates are quoted in thousands of bits, and 8 million bits is one decimal megabyte. The photo limit of 8,388,608 bytes is a server count, not a video bitrate. Do not paste a video estimate into the photo field and call it the upload check.
What the two published videos actually weigh
There are two public FashionUGC videos on this site. Both are 10 seconds and 9:16. The bronze gown file, made from a studio photograph of a mannequin, is 3,097,374 bytes. The floral midi file, made from an on-body photograph, is 3,155,730 bytes. Those counts are the files as published. They are not a bitrate in the create form, and the next job can be lighter or heavier.
Turn the bronze count back into an average rate to see what the formula means after the fact. 3,097,374 bytes times 8 is 24,778,992 bits. Divided by 10 seconds is 2,477,899.2 bits per second, about 2,477.9 kilobits per second across that whole file, container included. The floral file is 3,155,730 times 8, divided by 10, which is about 2,524.6 kilobits per second average. If you type 2478 and 10 into the calculator with audio at 0, you will land near the bronze byte count and not on it exactly, because the average folded the container into the rate, and because 2,477.9 is not the same as 2,478. Near is the right word. Exact is the file properties.
Neither average is a quality grade. The floral file is a little larger. That does not mean the print is more faithful than the gown, or the reverse. One still is a busy floral on a body. One is a metallic gown on a mannequin that the video then shows worn. Complexity in the picture can change how many bits an encoder spends. This page is not claiming that is why these two differ by 58,356 bytes. The difference is simply what the two files are. Look at the cloth when you play them. The examples are where those files sit next to the source photographs.
The preview JPEGs are a third set of numbers and must not be added to the MP4. The bronze source JPEG is 14,568 bytes. Two of its frames are 53,844 and 57,294 bytes. The floral source JPEG is 46,862 bytes. Two of its frames are 106,478 and 102,760 bytes. A frame JPEG is a still extracted for the page. The motion is the MP4. Quoting 53,844 bytes as the video size would be wrong by a factor of about fifty on the bronze file.
Use the pictures to keep the objects separate. The still you upload is the photograph. The frames are moments from the result. The byte count that matters for delivery of the video is the MP4 you download. The calculator sits in front of all three: it will estimate a size for a rate you invent, and it will not open the gown file to prove the 3,097,374. That proof is the measurement already written here, for these two files only.
Bitrate is not a picture of the dress
A higher rate can keep more of what the encoder decided to keep. It cannot restore a hem the photograph never showed, and it cannot make a blurry still sharp. If the source is soft, a 8,000 kilobit file of that softness is a heavy copy of a weak picture. Spend the effort on a clearer photograph, which is the product photo guide, not on a larger number in this form.
A lower rate can be enough when the frame is simple: a gown against a plain ground, a short duration, a viewer on a phone. It can also break a fine print into blocks. The floral dress is the kind of picture where you would notice that damage. The way to notice it is to play the file, not to require 8,000 kilobits because a blog once called that “high quality.” This site is not publishing that requirement.
Resolution and bitrate are different levers, and this calculator has no resolution field on purpose. FashionUGC does not state that a download is 720p or 1080p. A 9:16 shape can be many pixel sizes. The aspect ratio calculator names the shape. A file can be the right shape, a modest bitrate, and still a clear garment, or the right shape, a high bitrate, and a wrong neckline. Review the garment after the size estimate, not instead of it.
MDN’s overview of video codecs is the background for why two files of the same duration can differ. The codec is the method that turns pictures into bits. This calculator does not ask which codec you will use. It assumes the rate you typed is the rate the method hits, on average. Real encoders miss that average a little. That miss is normal. A miss of two megabytes on a ten-second file means the rate you typed was not the rate you got.
Colour, grain, and a busy street in the still all give an encoder more to spend bits on. FashionUGC is not a street generator. If the photograph is a plain ground, the file has less incidental detail than a snapshot of a shop floor. Do not compare a 3 MB gown file with a 12 MB clip of a crowd and conclude the gown was under-encoded. The scenes are not the same amount of change from frame to frame. Ten seconds of a slow cloth move is not ten seconds of a cut every half second.
Sound, captions, and the size they add
The generated MP4 has no soundtrack. An audio rate of zero matches that file. A voiceover or a music bed is an edit you do later, if you have the right to use the sound. The creative ideas page is where those rights are spelled out. This calculator only adds the kilobits you type. It does not pick a song, and it does not check a licence.
Speech is often a low rate next to the picture. One hundred and twenty-eight kilobits per second of audio for 30 seconds is 480,000 bytes, under half a decimal megabyte. The picture at 2,500 kilobits for those same 30 seconds is 9,375,000 bytes. The voice is the smaller part of the file and the part a false claim can still ride in. Size is not a truth test. A short false sentence fits in a small audio stream. The script word calculator is about how many words fit. Neither tool decides whether the words are true of the garment.
Captions burned into the picture can make the file slightly larger because the letters are extra detail, and they can hide the print. FashionUGC does not burn them in. A caption track inside a player, rather than painted on the cloth, is another small stream. Do not plan your bitrate around captions. Plan the picture so the dress is visible, then add words off the cloth.
Two files of the same garment at two lengths are two generations. A 10-second file at a given rate is about one third of a 30-second file at that same rate, if the encoder actually holds the rate. You pay for the length, at ₹149, ₹199, ₹279, ₹349, or ₹500, not for the megabytes. A heavier 10-second download does not move you into the 15-second price. A light 30-second download does not become a 10-second price. The byte estimate and the invoice are separate.
Limits that are not this formula
Platforms publish their own ceilings for uploads. Some care about duration, some about ratio, some about a maximum file size, some about a minimum length. A calculator result inside a ceiling is not proof the file is allowed. The marketplace guide collects the differences that matter for clothing listings, including minima a 10 to 30 second file does not meet. Read that page for the rule. Use this page only to see whether a bitrate you chose is even in the neighbourhood of a size you were given.
Google’s Merchant Center documents an optional video link with requirements that include length, ratio, and a maximum file size, and a pixel floor this site does not claim your download will meet. If you are filling that attribute, the help page is the spec. An estimate of 15 decimal megabytes does not tell you the ratio is 9:16, 16:9, or 1:1, and it does not tell you the pixel count. Check the file you will paste into the feed.
The photograph you upload is under a different ceiling, 8,388,608 bytes, and only for JPEG, PNG, or WebP. A 3 MB video is not a 3 MB photo. A 7 MB photo is not a prediction of the video. People mix them because both are “the file.” The photo calculator and this one are split so the mix is harder. Six photos can each pass 8 MB and the resulting MP4 can still be whatever size the encoder produced.
Email is a bad place for either file when it is large. A 9 MB video as an attachment is how a launch lands in spam or bounces. The launch and email page says to host the file and link it. The size estimate tells you whether an attachment was a bad idea. It does not make the inbox play the MP4.
Search pages want the picture and the words to name the same product. Google’s image guidelines are about that match. A lightweight video of the right dress is a better page than a heavy video of a different dress. Compress or leave the rate alone based on whether the cloth survives, then write the title for the cloth that survived.
Mistakes this page is here to catch
The first mistake is reading 2,500 kilobits per second as the FashionUGC export setting because it was the default in the box. The default is a round planning number near the average of the two published files, so the first result is a familiar size. Change it. The product will not follow the field.
The second mistake is adding the JPEG previews to the MP4. The page shows both so you can see they are different objects. A delivery spreadsheet that sums 3,097,374 and 53,844 has double-counted one moment of the gown.
The third mistake is using decimal megabytes and the photo megabyte as if they were identical. 8 decimal megabytes is 8,000,000 bytes. The photo limit is 8,388,608 bytes. Close, and not the same test. This tool states which unit it used. Do not strip the word “decimal” when you copy the number into a spec.
The fourth mistake is a soundtrack in the estimate of a silent deliverable. If the file you will hand over has no audio, the audio field stays 0. A 128 kilobit bed you might add next week is a different file. Estimate the file you are actually sending.
The fifth mistake is a quality story. “We used 8,000 kilobits, so the silk is accurate” is not a sentence this arithmetic supports. Accuracy is the hem, the colour, and the print against the photographs. A huge file of a wrong neckline is an expensive wrong neckline.
The sixth mistake is a 60-second estimate treated as a product you can buy. You can calculate it. You cannot generate it here. The longest export is 30 seconds. A marketplace that wants a minute wants a different source, which the marketplace guide already says.
The seventh mistake is blaming the container for a file that is twice the estimate. A small wrapper does not double a ten-second clip. If the download is double, the rate was about double, or the duration was about double, or you added a stream you forgot. Re-read the file. Re-run the formula with the duration the player shows.
A short way to brief the size
Write the duration you will actually generate, from the sold lengths. Write the rate you are using only as a planning guess, or leave the rate blank in the brief and fill the byte count after the download. If a partner gave you a maximum size, put that size in the target field, read the kilobits per second, and treat it as a ceiling to check after export, not as a dial on the create form. There is no bitrate dial.
When the MP4 is in hand, write its real byte count next to the estimate. If they are close, the guess was lucky or familiar. If they are far apart, keep the real number and drop the guess. The next colourway should not inherit a fake precision. The garment changes. The encoder’s average can change. The only stable facts in the brief are the length you bought, the frame you chose, and the photographs of that one piece.
Then play the file. If the cloth is clear and the size is inside the partner’s ceiling, you are done with this calculator. If the cloth is clear and the size is over the ceiling, that is an editor or a re-export problem, not a reason to describe a different dress. If the cloth is wrong, the size does not matter yet. Fix the pictures or reject the file before you spend another hour on kilobits.
