Skip to main content

The Rise of Google, Part 12: Buying YouTube

Buying YouTube

🎬 Prefer to watch? Here's the 60-second version:

Watch on YouTube ▶

📚 The Rise of Google — a 20-part series. See all parts »  |  « Part 11: The Product Explosion

In the autumn of 2006, the hottest property on the internet was run by roughly sixty-five people working above a pizzeria in San Mateo, California. It had launched publicly only eighteen months earlier. It made almost no money. And on October 9, Google agreed to pay $1.65 billion for it — every dollar in Google stock, not a cent in cash. The company was YouTube, and the deal would become one of the smartest acquisitions in the history of technology. At the time, plenty of very smart people were certain it was one of the dumbest.

Nineteen months, sixty-five people

YouTube was born in February 2005 out of a familiar frustration. Its three founders — Chad Hurley, Steve Chen, and Jawed Karim — had all worked at PayPal, and like a whole generation of the “PayPal Mafia,” they went looking for the next problem to solve. The story they later told was that sharing video online was absurdly hard: no easy way to upload a clip, no reliable way to watch one without the right codec and a lot of patience. So they built the missing piece.

The first video went up on April 23, 2005. It was nineteen unremarkable seconds of Karim standing in front of the elephant enclosure at the San Diego Zoo, observing that elephants have “really, really, really long trunks.” It was titled Me at the zoo, and it is still online today. From that flat beginning the site did something few products ever do: it went vertical. Backed by about $11.5 million from Sequoia Capital — whose partner Roelof Botha was, naturally, another PayPal alum — YouTube rode the twin waves of cheap bandwidth and the embeddable player. Anyone could drop a video into a MySpace page or a blog, and suddenly the whole web was a screen.

By the time Google came calling, YouTube was serving more than 100 million video views a day and absorbing roughly 65,000 new uploads every twenty-four hours. It had become a verb. It had also, crucially, become expensive — the bandwidth and storage bills for all that video were enormous, and the revenue to cover them essentially did not exist.

Google already had a video site

Here is the part that gets forgotten: Google was not a spectator to online video. It had launched Google Video in January 2005 — actually a few months before YouTube opened to the public — and had poured real effort into it. Google Video could host clips, sell downloads, and search television transcripts. On paper it had everything: Google’s infrastructure, Google’s search expertise, Google’s money.

What it did not have was YouTube’s culture. Google Video felt like a library; YouTube felt like a party. Users flocked to the scrappy upstart and its comment threads and its endless stream of the strange, the funny, and the homemade. Google’s leadership — Eric Schmidt, Larry Page, and Sergey Brin — watched their own product lose the race to a company a fraction of its size, and drew the conclusion that would define Google’s next decade: when you cannot out-build the thing, buy it. The negotiations moved fast, reportedly hammered out over a single weekend. By November 13, 2006, the acquisition had formally closed.

Rather than fold YouTube into the mothership, Google left it almost entirely alone — same brand, same team, same offices, same irreverent identity. Hurley and Chen filmed a giddy, hand-held thank-you video for their users, joking that “the king of search” and “the king of video” had joined forces. It was awkward and earnest and went, of course, viral.

The moron premium

The applause was far from universal. To skeptics, Google had just paid an absurd sum for a site with no profits and a legal time bomb ticking inside it. Billionaire investor Mark Cuban had said weeks earlier that only a “moron” would buy YouTube, because the site was riddled with copyrighted clips its users had no right to post — and whoever owned YouTube would inherit every one of those lawsuits.

He was not wrong about the lawsuits. In March 2007, Viacom sued Google for $1 billion, alleging that some 160,000 unauthorized clips of its shows had been viewed more than a billion times. The case dragged on for years and became a landmark test of the “safe harbor” provisions of the Digital Millennium Copyright Act — the rule that a platform is not liable for what its users upload, provided it takes infringing material down when notified. Google ultimately prevailed, and the two companies settled in 2014 with no money changing hands.

That legal shield mattered enormously, but the real vindication was economic. Google’s answer to the copyright problem was not just lawyers; it was engineering. The company built Content ID, a fingerprinting system that let rights holders find their material and choose to block it — or, far more often, to leave it up and collect the ad revenue. Copyright liability quietly became a copyright business. YouTube grew into a platform that would eventually generate tens of billions of dollars a year, more than Google paid for it every few weeks. The $1.65 billion that looked reckless in 2006 turned out to be a rounding error against what it bought.

Google had learned that its greatest strengths — infrastructure, search, and a willingness to wait years for a bet to pay off — could be pointed at things it had not invented. It was a lesson the company was about to apply to something far bigger than video: the phone in your pocket. Next time: the operating system Google gave away for free, and the war it started.


🔗 Explore more from Syncster

Comments

Popular posts from this blog

Cursor AI Review: Is the AI Code Editor Worth It?

I've been using Cursor as my main code editor for a while now, and enough people have asked whether it's worth switching to that a proper review felt overdue. Short version: for me, yes — but with caveats. What is Cursor? Cursor is an AI-first code editor built as a fork of VS Code. That means every extension, theme, and keybinding you already use in VS Code works here, but with AI woven directly into the editing experience instead of bolted on as a plugin. It's made by Anysphere and can run models from OpenAI and Anthropic under the hood. What I like Tab completion is uncanny. Cursor predicts your next edit — not just the rest of the line, but the next change across the file. Once you get used to hitting Tab, going back to a plain editor feels slow. The Composer / Agent mode. You describe a change in plain language and it edits multiple files at once, showing you a diff to accept or reject. For refactors and boilerplate, this saves real time. It unde...

MacBook Pro M5 vs M5 Pro: Which One Should You Actually Buy?

Apple's latest 14-inch MacBook Pro comes in two very different flavors: the base M5 and the step-up M5 Pro . On paper they look similar — same gorgeous Liquid Retina XDR display, same design — but under the hood the gap is bigger than the names suggest. Here's a clear, no-hype breakdown, with concrete use cases so you can match the chip to your work. Quick spec comparison Spec M5 M5 Pro CPU 10-core (4 performance + 6 efficiency) Up to 18-core (6 performance + 12 efficiency) GPU 10-core Up to 20-core Neural Engine 16-core 16-core Memory bandwidth 153 GB/s 307 GB/s (roughly double) Unified memory 16 / 24 / 32 GB 24 / 48 / 64 GB Max storage Up to 4 TB SSD Up to 8 TB SSD Battery (video playback) Up to 24 hours Up to 22 hours Media engines Single encode/ProRes engine More encode/ProRes engines (higher configs) What actually changes between them More cores — the M5 Pro nearly doubles CPU cores and adds GPU cores, so sustained, multi-threaded work finishe...

How I used Google Sheets and Apps Script

Google Sheet is one of the most powerful spreadsheet application that exists online, rivaling with Microsoft's Excel. One of the main strengths is its strong support for collaboration with other users, much easier and popular than collaboration tools with Microsoft Office. Aside from plain spreadsheet, it also supports extensions such as macro. If you are familiar with macros on other office tools, they work almost the same. However, the most extension I use and tinker with is the Apps Scipt . Apps Script Extension One of the challenges I faced recently is how do I track or monitor reports in our department if they are submitted on time or worst, forgotten due to lack of better monitoring tools. So I thought if there can be simple applications that can be deployed or use by a more general user to allow reminding periodically what reports are approaching due dates or those that are past dues. Then I looked for a way, instead of creating a full blown app from scratc...