How to convert video bitrate from Mbps to kbps

What to do

Multiply Mbps by 1,000 to get kbps. Divide kbps by 1,000 to get Mbps. These bitrate units use decimal prefixes, while file size can use decimal MB or binary MiB.

Convert and verify the encoder field

Multiply 8.141 Mbps by 1,000 to get 8,141 kbps. Write the units beside both values and read the encoder's expected unit before entering one. If the field asks for an average, do not enter the value in a peak or streaming setting instead. When comparing file sizes, distinguish MB from MiB independently. Inspect the exported file's reported average to see how closely the encoder followed the target.

Example or check

8.141 Mbps is about 8,141 kbps. If your editor expects kbps, enter the kbps result without typing a unit suffix into a numeric field.

Related checks for video export and bitrate

Separate average and peak bitrate

An average bitrate is useful for predicting total size. A peak bitrate describes short periods when the encoder may use more data. Variable bitrate can distribute bits differently across easy and difficult scenes. A talking head against a plain wall is usually easier to encode than fast movement, fine foliage, or grain. Two files with the same duration and target bitrate can differ in quality or actual size. Review a difficult scene before settling on a preset. If live streaming is the goal, use the current settings for that platform and consider upstream stability as well as average throughput.

Understand bits, bytes, and prefixes

Network and encoder bitrates are usually described in bits per second. File size is usually described in bytes. There are eight bits in one byte. Decimal MB uses one million bytes, while MiB uses 1,048,576 bytes. If you read a size from a system that rounds or labels binary units ambiguously, use the raw byte count where available. Bitrate prefixes stay decimal in this calculator, so one Mbps equals one thousand kbps. Keep the unit with the number when recording a preset or sharing a result. The same digits in Mbps and kbps differ by a factor of one thousand.

Use the budget equation carefully

Convert the target file size to bits and divide by the number of seconds to get the combined average budget. If you reserve a portion for the container, subtract that reserve and then subtract the combined audio bitrate. The remainder is the budget for video. In the other direction, add average video and audio bitrates, multiply by runtime, and divide by eight to estimate bytes. The simplest formula is useful for planning, but it does not include container details unless you allow for them. Zero duration is invalid because there is no meaningful bitrate to calculate.

Work through a sample export

For an eight-minute video, use 480 seconds. A decimal 500 MB cap represents 4,000,000,000 bits. Dividing by 480 gives about 8.333 Mbps total. Subtracting 0.192 Mbps audio gives about 8.141 Mbps video with no overhead reserve. With a two-percent reserve, the video allowance drops to about 7.975 Mbps. If the destination enforces a hard limit, choose a conservative result and inspect the rendered bytes. If the encoder uses kbps, multiply the Mbps value by one thousand and keep the units straight when entering it.

Decide how much audio to budget

Use the sum of the audio bitrates for tracks that will be stored in the output. A single track at 192 kbps uses 0.192 Mbps, while two tracks at that rate use twice as much. Keep enough audio quality for the material and device, and verify that the right tracks were exported. A silent track can still take space if it is encoded as audio. If the tool returns a negative video budget, adjust the cap, length, or audio allocation. Do not enter a negative or zero result into an encoder and expect it to make a useful video.

Define the limit before choosing settings

Start with the reason you need a specific file size. A client delivery portal, a slow upload, and an archival master have different priorities. If a limit is strict, keep a margin rather than targeting the final byte exactly. Write down the runtime of the rendered cut, including the ending, and identify how many audio tracks are included. A tool can estimate a workable average bitrate, but the video encoder still decides how bits are spent across frames. Save your high-quality master separately so delivery constraints do not make it impossible to recover detail later.

Inspect the export instead of guessing

After rendering, check file size, duration, frame dimensions, and a few representative scenes. Verify the beginning and ending as well as a segment with motion or small type. If the file is too large, see whether the actual average was higher than the target or whether a second audio track was included. Export from the master again rather than re-encoding the constrained copy repeatedly. Keep a note of the encoder settings and actual outcome. If quality was poor at the required size, compare a lower resolution or different codec supported by the destination before committing to another long render.

Save presets with context

Write down resolution, frame rate, codec, approximate average video bitrate, audio settings, and the reason for the preset. Label presets for the destination rather than by a vague quality name. If a client changes the upload cap, calculate a new budget from the actual runtime instead of reusing last month's settings. Verify the output on the target player when possible. A small record of predicted and observed sizes will show whether a margin works for your encoder and projects. Preserve a separate master or editable project for future outputs that need different settings.

Compare two presets with a difficult scene

Pick a short portion that contains motion, fine texture, or a gradient. Export it at the two target settings you are considering. Play both at the size the viewer will see and compare detail around movement and text. A small representative test can prevent a long re-render with an unusable bitrate. Do not multiply a single easy scene's compressed size and expect an exact result for the whole video. Check the full output after selecting a preset, especially when a client portal enforces a maximum file size.

Plan the upload separately

The data rate used to encode a file is not the same as the network rate used to upload it. After export, use the file's actual size and your measured upstream speed to estimate transfer time. Leave room for variations, retries, and platform processing. If you are under a deadline, start the upload early enough to review playback and make corrections. For YouTube delivery, refer to the official upload encoding recommendations for the actual resolution and frame rate. A file that fits a size limit still needs to satisfy the technical and editorial requirements of its destination.