Mochi Media Built an Ad Network That Lived Inside the Game's Preloader

What MochiAds Actually Did

Mochi Media launched its MochiAds service in 2006, targeting the same developers who were already distributing games through portals like Newgrounds and Miniclip. The pitch was straightforward: embed a small SDK into the game's SWF, and the preloader — that brief loading sequence every Flash game already had — becomes a paid advertising slot. No exclusive deal with a portal, no sponsorship negotiation. A developer uploaded their game, integrated the MochiAds ActionScript library, and collected revenue each time the ad ran, wherever the game was hosted.

The mechanism worked by intercepting the preloader's natural pause. While the SWF's assets loaded across a user's connection, the MochiAds SDK would call out to Mochi's ad servers and serve a short interstitial — typically a graphical display ad, later including video. The call was handled client-side, inside the running Flash Player, and required no server infrastructure from the developer. File size overhead was minimal: the SDK added only a few kilobytes to the SWF. Because Flash games spread virally across hundreds of hosting sites, the same SWF carrying the same ad tag would keep generating impressions regardless of where it had been copied — a property no conventional banner network could replicate.

The Payment Model and Its Limits

MochiAds operated on a CPM basis — cost per thousand impressions — and split revenue with developers. Mochi's publicly documented rate was a 50/50 split, with the developer receiving half of whatever the ad inventory sold for. CPM rates fluctuated with advertiser demand and the game's audience demographics, but developers discussing earnings on forums consistently reported figures in the low single digits per thousand plays during the network's peak years, roughly 2007 to 2012. For a modestly successful game accumulating millions of plays across the web, that arithmetic could produce meaningful independent income — not a salary, but enough to fund the next project.

The ceiling was real, though. MochiAds revenue was tied to raw impression volume, which meant it rewarded games that spread widely rather than games that held a dedicated audience. A deeply engaging game played repeatedly by a smaller group generated fewer impressions than a shallow title that went viral once. Developers who combined MochiAds with a portal sponsorship — using the loading-screen logo as a contract from one buyer while collecting ad revenue everywhere else the game appeared — often earned more in total than either route alone.

Scale, Acquisition and Collapse

At its peak Mochi Media claimed its network reached tens of millions of players monthly across thousands of games, making it the largest Flash-specific ad infrastructure in operation. The company attracted venture funding and expanded beyond ads into leaderboards, virtual currency tools, and developer analytics, all delivered through the same SDK embedded in the SWF. The ambition was to become indispensable infrastructure for the Flash ecosystem rather than merely an ad broker.

Shanda Games acquired Mochi Media in 2010. The acquisition did not stabilise the business. As browser vendors began restricting the NPAPI plug-in architecture that Flash Player depended on, and as mobile advertising budgets pulled spend away from browser-based games, the CPM rates developers received fell sharply. Shockwave shut Mochi Media down in March 2014, giving developers roughly two weeks' notice. Payment processing ceased, archived leaderboard data became inaccessible, and the ad-serving infrastructure went dark. Any SWF that had not been recompiled to remove the SDK would now stall at the preloader, waiting for an ad server that no longer responded — a particularly visible form of link rot baked into the game file itself.

The shutdown illustrated what the MochiAds model had always required: a live network call at launch, every launch, forever. The games had always depended on Mochi staying on. When it did not, the dependency showed.