Container Overhead
Container overhead is the space used to organize and describe media in addition to its encoded picture and sound.
A transport packet makes the cost of organization visible. A basic MPEG-TS packet occupies 188 bytes. Its minimum header occupies four, leaving at most 184 for the remaining packet data.
minimum header fraction = 4 ÷ 188 = approximately 2.128%
To carry a simplified one million payload bytes using full 184-byte payload spaces requires ceil(1,000,000 / 184) = 5,435 packets. Those packets occupy 1,021,780 bytes. Their headers occupy 21,740 bytes, and the final packet has 40 bytes of otherwise unused space in this simplified accounting.
This is a worked minimum-header example, not a total overhead prediction for a real TS. Actual adaptation fields, programme tables, packet filling, and other structures change the allocation.
Repeated costs and one-time costs
| Organizational cost | How it contributes |
|---|---|
| Track descriptions and codec setup | Usually a small amount compared with a long movie |
| Per-packet framing | Repeats as more media packets are stored |
| Timing, sample tables, and seek indexes | Grows with the media organization |
| Padding or reserved space | Allocates space for layout or later updates |
These bytes are container overhead: information or space needed around the encoded media. The encoded video and soundtrack have their own sizes before this additional packaging is considered.
Packaging savings versus removed media
Suppose a remux copies the same selected video and audio into a format with different packet grouping and index structures. The whole output can have fewer bytes even though its decoded picture and sound are unchanged. The difference belongs to packaging.
Now remove a 384 kb/s soundtrack lasting two hours. That eliminates 345.6 MB of encoded content, not merely overhead. Similarly, removing a large font or cover attachment changes stored resources. To understand a size difference, account for selected components before comparing the organizational cost.
Overall file bitrate includes container bytes because it divides total file size by duration. A network transfer adds HTTP, transport, and link costs outside the file. An Emby delivery estimate therefore needs to identify whether a rate describes encoded streams, the whole packaged file, or network traffic.
The distinction prevents a shorter remux from being mistaken for a better video encode: fewer organization bytes and a changed representation of the picture are different improvements.