A closer look at the costs (and fine print) of H.264 licenses

By | January 17, 2011, 5:37pm PST

I read license agreements so that you don’t have to.

This weekend, I’ve been digging deep into the agreements that govern your right to encode and decode video content using the AVC/H.264 standard. Google’s announcement last week that it intends to remove H.264 support from its Chrome browser didn’t mention the word money at all. The original terse announcement raised more questions than it answered, which led Google product manager Mike Jazayeri to follow up on Friday with a second blog post, four times as long as the original. This time, he didn’t duck the subject of pay-to-play and H.264:

To use and distribute H.264, browser and OS vendors, hardware manufacturers, and publishers who charge for content must pay significant royalties—with no guarantee the fees won’t increase in the future. To companies like Google, the license fees may not be material, but to the next great video startup and those in emerging markets these fees stifle innovation. […]

Our choice was to make a decision today and invest in open technology to move the platform forward, or to accept the status quo of a fragmented platform where the pace of innovation may be clouded by the interests of those collecting royalties. [emphasis added]

That raises a host of interesting questions that can only be discussed intelligently if one understands exactly who’s paying, and how much. The group that licenses the AVC/H.264 patent portfolio, MPEG LA, publishes a summary of the license terms. I first looked at that document last May and published an analysis here, in H.264 patents: how much do they really cost? This post is an update to that information.

The agreement that I examined last May expired a few weeks ago, at the end of 2010. The renewed agreement, which is now available on the MPEG LA web site (PDF format) covers a five-year term from 2011 through 2015. According to the document properties, this version was last updated on January 5, 2011.

Using Microsoft Word, I compared the January 2011 version with a copy I saved back in May 2010. This post summarizes the current licensing terms and points out one eyebrow-raising change, which literally appears in the fine print at the end of the document.

To use H.264 features, you must have a valid license for MPEG LA’s AVC/H.264 Patent Portfolio License. This is how the MPEG LA describes that portfolio:

[E]ssential patent rights for the AVC/H.264 (MPEG-4 Part 10) digital video coding standard used in set-top boxes, media player and other personal computer software, mobile devices including telephones and mobile television receivers, Blu-ray DiscTM players and recorders, Blu-ray video optical discs, game machines, personal media player devices, still and video cameras, subscription and pay-per view or title video services, free broadcast television services and other products. To align with the real-world flow of AVC/H.264 commerce, reasonable royalties are apportioned throughout the AVC/H.264 value chain.

Chances are, you’re already licensed to use AVC/H.264. You may even have paid, indirectly, several times on a single PC.

MPEG LA neatly divides its customers into two categories and publishes royalty rates for different groups within each category.

Group (a) consists of companies that “manufacture and sell AVC encoders and decoders,” typically as part of a hardware or software product. These companies pay MPEG LA for a license. In exchange, their customers get the right to use the codecs supplied with that software “for personal and consumer (including internal business) purposes without remuneration but not for other uses.” The parenthetical language about internal business use was added in the most recent update.

Group (b) applies to “video content or service providers,” who need sublicenses to use AVC encoders and decoders to deliver H.264-formatted video that does not fall under the “personal and consumer” license.

On the next page, I take a closer look at what H.264 licenses really cost software companies like Google.

Page 2: Who pays for an H.264 license? And how much does it cost? –>

Topics

Ed Bott is an award-winning technology writer with more than two decades' experience writing for mainstream media outlets and online publications.

Disclosure

Ed Bott

Ed Bott is a freelance technical journalist and book author. All work that Ed does is on a contractual basis.

Since 1994, Ed has written more than 25 books about Microsoft Windows and Office. Along with various co-authors, Ed is completely responsible for the content of the books he writes. As a key part of his contractual relationship with publishers, he gives them permission to print and distribute the content he writes and to pay him a royalty based on the actual sales of those books. Ed's books are currently distributed by Que Publishing (a division of Pearson Education) and by Microsoft Press.

On occasion, Ed accepts consulting assignments. In recent years, he has worked as an expert witness in cases where his experience and knowledge of Microsoft and Microsoft Windows have been useful. In each such case, his compensation is on an hourly basis, and he is hired as a witness, not an advocate.

Ed does not own stock or have any other financial interest in Microsoft or any other software company. He owns 500 shares of stock in EMC Corporation, which was purchased before the company's acquisition of VMWare. In addition, he owns 350 shares of stock in Intel Corporation, purchased more than two years ago. All stocks are held in retirement accounts for long-term growth.

Ed does not accept gifts from companies he covers. All hardware products he writes about are purchased with his own funds or are review units covered under formal loan agreements and are returned after the review is complete.

Biography

Ed Bott

Ed Bott is an award-winning technology writer with more than two decades' experience writing for mainstream media outlets and online publications. He's served as editor of the U.S. edition of PC Computing and managing editor of PC World; both publications had monthly paid circulation in excess of 1 million during his tenure. He is the author of more than 25 books on Microsoft Windows and Office, including the recently released Windows 7 Inside Out.

Talkback Most Recent of 24 Talkback(s)

  • "I read license agreements so that you donâ??t have to."
    And this is why I love reading your posts and I've been following your blog for years.

    Keep posting on a regular basis, you're a true journalist in a field of people who can operate gadgets but can't analyse a legal document, a business report, or even a press release.
    ZDNet Gravatar
    LB75
    17th Jan 2011
  • RE: A closer look at the costs (and fine print) of H.264 licenses
    Well that explains why I support this move by google. However, I think they need to get on the ball with WebM project. WebM should be a technologically superior codec to h.264 and h.265.
    ZDNet Gravatar
    AdonisSMU
    17th Jan 2011
  • Please explain
    Good post Ed.

    AdonisSMU: How has what Ed's posted support Google's move?

    The license fees are small change and the fee increases for the next 5 year are capped at 10%.

    WebM isn't technically superior to H.264, it's not even as good, and has zero hardware support (which takes a very long time).

    In addition WebM are likely to be patent encumbered, google doesn't provide patent protection, nor is their a way to easily license such patents.

    Where's the support for Google's move?
    ZDNet Gravatar
    Richard Flude
    17th Jan 2011
  • The fact that there is even "fine print" is the problem
    Do you remember the 27-page legal contract you signed when you bought that Sony Trinitron back in the 90's? Or the 10-page contract you had to agree to before playing Scrabble for the first time? Neither do I.

    But the corporations who started with "shrink-wrap" licenses for software have now built them into almost every consumer gadget imaginable, including TVs, media players, and even car stereo systems. That's not to mention every computer, cellphone and website on the planet.

    The upshot is that the average "techie" consumer is now party to hundreds or thousands of new contracts each year, and is responsible for knowing and following the letter of each of those contracts. Are they enforceable? Yes, according to most law professors surveyed in a 2006 Carnegie-Mellon study. Even if the contracts (sometimes known as "EULA" or "Terms of Service") have one-sided or egregious terms, they can be enforced to the extent of giving the average consumer pains in both the head and the pocketbook.

    My dad always told me to read before I sign, but that is no longer even physically possible in today's world. You are faced with the choice of spending half of your waking hours reading contracts, or simply becoming a Luddite and eschewing the technological world altogether. The chances of getting any legislative relief are zero, in fact the opposite is true: Congress is bent on weakening more consumer rights and favoring their corporate donors and the legal profession.

    Will it change? Maybe, by the time contracts have started including clauses granting the corporations unlimited access to your bank account and ius primae noctis (look it up) for your daughters.
    ZDNet Gravatar
    terry flores
    17th Jan 2011
  • Enforcement questionable
    Terry there's substantial evidence the Eula would not be as enforceable as often proclaimed. But even if they are you must consider likely damages awarded for breaches. An individual offending a clause in their h.264 license is unlikely to be causing recoverable damage beyond the license fee, a manufacturer or distributor one the other hand is a target worth persuing.

    This is recognized in the minimum license clauses.

    Just click agree and move on, unless you're looking for prizes:

    http://yro.slashdot.org/article.pl?sid=05/02/23/2315211
    ZDNet Gravatar
    Richard Flude
    17th Jan 2011
  • RE: A closer look at the costs (and fine print) of H.264 licenses
    @terry flores
    I hope someone would challenge the validly of the agreements very soon. On the basis that every body knows the users don't read them and practically can't. On the basis that there are other way to do this and the sellers don't use them. In a way they hide their contracts in a lot of words offered in an inconvenient moment. Like when users are installing, not when users are selecting a product.

    I hope that may inspire the creation of a limited number of certifications for those agreements. Certifications about property's of those agreements that everybody can understand fast.
    ZDNet Gravatar
    bezoeker
    18th Jan 2011
  • Exactly
    @terry flores

    There are things which are more important than money. FREEDOM for one.

    The idea of making an encumbered codec a web "standard" is insane.

    Software patents will ensure that the US ceases to be the World's technology innovation leader.
    ZDNet Gravatar
    Tim Patterson
    18th Jan 2011
  • RE: A closer look at the costs (and fine print) of H.264 licenses
    "A company that sold or gave away 200 million licensed products in a single year would see its bill triple, paying roughly $22 million at the 11-cents-per-copy rate."

    That would be a fun problem to have.

    By the way, excellent post.
    ZDNet Gravatar
    Rich Miles
    17th Jan 2011
  • RE: A closer look at the costs (and fine print) of H.264 licenses
    ifunia encode and decode video for apple users with H.264 standard in most of their products, but not pay any sort of fees to them.
    ZDNet Gravatar
    John Titlow
    18th Jan 2011
  • Stop the insanity of software patents
    Software is algorithms.
    Algorithms is mathematics.
    Software ist mathematics? Jawohl!


    Donald Knuth was right.
    h-t-t-p://www.pluto.it/files/meeting1999/atti/no-patents/brevetti/docs/knuth_letter_en.html

    God bless Google.
    ZDNet Gravatar
    Dietrich T. Schmitz, ~ Your Linux Advocate
    18th Jan 2011
  • RE: A closer look at the costs (and fine print) of H.264 licenses
    @Dietrich T. Schmitz, Your Linux Advocate
    I have two notebook computers, both dual boot - Win7 + PC Linux on one, Win7+ Puppy Linux on the other. Each OS has software for which a paid license is required. Yes, there can be licensing fees charged even if the OS is 'open source'. Remember that not all Linux users are IT tech's. Some Linux users want the advantages Linux offers, but lack the coding savvy and time required to make open source software meet their needs. They'll gladly pay a licensing fee for software that makes their life easier - even if the software is opensource-based. They are not 'paying' for open source software - they are paying for the time and talents of a developer that will free resources that can be better used elsewhere.
    ZDNet Gravatar
    nkfro
    18th Jan 2011
  • Eco argument, the cost of innefficient codecs
    Youtube serves about 750 billion video's per year.
    About 3000 billion minutes of video.
    VP8 videocodec is less efficient than h.264.

    Let's put the energy cost up for that say 0.05 Wh for the extra transport cost per minute of video and an extra 0.1 Wh for playing the video per minute*.
    That would just mean that a descision for Google to move all of youtbue to WebM with the VP8 codec would cost a staggering 450 billion Wh extra energy compared to using the h.264 codec.

    Not a very green choice by Google.


    * actually I measured more than a 6W increase for playing a quality WeBM trough html5 in Firefox compared to playing the same video h.264 trough IE9. h.264 is much less demanding if a computer supports hardware decoding.
    ZDNet Gravatar
    IE9
    18th Jan 2011
  • Naiveté
    The MPEG-LA members are for profit enterprises, some of which have been pretty ruthless and even acted illegally in the past. If this whole codec business were not ultimately about the money, they could just open source it and be done with it. They would have no administrative costs.

    This is about making money directly from IP or indirectly from controlling a market and sell related products. I just do not see any compelling reason to get involved unless you have to, your protestations that it is just "pocket change" notwithstanding.

    Oh, and I have a bridge I could sell you. I could also sell you some crack for cheap for a while, with "reasonable" price increases, once you are hooked.
    ZDNet Gravatar
    Economister
    18th Jan 2011
  • RE: A closer look at the costs (and fine print) of H.264 licenses
    @Economister

    Google is a for profit enterprise. They have been pretty ruthless and even acted illegally in the past. If this whole search business were not ultimately about the money, they could just open source it and be done with it.

    I use search a heck of a lot more than I watch video on the web. As search is a fundamental component of the web they should open source their search algorithms. You know, for the betterment of the web.
    ZDNet Gravatar
    Rich Miles
    18th Jan 2011
  • Bottom line
    Unless you want to pay for Chrome, I think Google has every right to include or exclude anything it wants. It's free.

    Why should they have to pay, when we won't?
    ZDNet Gravatar
    Hameiri
    18th Jan 2011

Talkback - Tell Us What You Think

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources