Advantages: No CPU spent on the renderer to compress and no CPU spent on the client to decompress. Usually very good for SD on good networks. Very good on clients with weak CPU and a good network card.

Disadvantages: HD requires a big amount of data, it typically takes longer to transfer over the network than compressed alternatives, and it uses a lot of network capacity.

Advantages: Compresses graphics very well. PNG compression has a very small footprint on very slow networks; for example, this is useful for Digital Subscriber Line (DSL) networks, 10Mbit networks, or district offices that render in a central location.

Disadvantages: May use a lot of CPU to compress and decompress - a problem on slower computers. Generally outperformed by the other two options and mostly useful for special cases.

Advantages: Compresses graphics well. Is easy and fast to compress and decompress. Uses a small fraction of the space for a 1080i field compared to no compression - network footprint is quite good. It often performs best for HD on fairly updated computers. Also does very well on 100Mbit networks. Has special handling that exploits the nature of TV-graphics and NLE graphics that contain big open areas, for example lower thirds, over the shoulders, and so on.

Disadvantages: Uses CPU on the renderer and the client, - less powerful machines might get better performance with no compression. The smaller amounts of data with SD negates some of the compression benefits, but can often be best for SD too. Might not provide much benefit for graphics with big horizontal gradients.