8mb - Shrek
The "Shrek 8MB" phenomenon is a legendary internet subculture challenge where tech enthusiasts use advanced video codecs to squeeze the entire 90-minute (2001) movie into a file size of exactly 8 megabytes. This specific target exists because
8MB was the original file size limit for non-Nitro users on Discord
, making it the "holy grail" of ultra-low-bitrate compression. The Technical Magic Behind the Meme
To make a full-length film fit into a space smaller than a high-resolution photo, enthusiasts use cutting-edge technology:
: This modern, open-source video format is the primary tool used for these "impossible" encodes because it offers superior quality at extremely low bitrates compared to older formats. Extreme Downscaling
: The resolution is typically crushed down to something tiny, like 144p or lower , resulting in a "crunchy," pixelated aesthetic. Audio Sacrifices : Audio is often mono and compressed to bitrates as low as 8–16 kbps
, making the iconic "All Star" opening sound like it's being played through a drive-thru intercom. Why Shrek? Meme Status
is the internet's favorite movie to experiment on, largely due to its "layers" of meme history. The Ultimate Test
: Compressing a colorful, fast-moving animated film is a "trial by fire" for new encoding software.
: Once compressed to 8MB, the file can be shared freely in Discord chats, allowing people to "watch" the entire movie in a tiny, vibrating box of pixels for the sake of the joke. While Discord eventually increased its file limits, the remains a benchmark for the AV1 community
—a digital ship-in-a-bottle that proves how far compression tech can go. a video yourself using
The swamp had a new stench. Not the familiar, comforting reek of mud, onion, and existential dread. This was sharper. Colder. It smelled like… waiting.
Shrek sat on his outhouse, which he’d dragged onto his front porch for optimal thinking. In his massive green hands, he held a floppy disk. It was gray, square, and utterly silent.
“Donkey,” Shrek said, not looking up. “Explain it again. Slowly. In small words. The kind they print on a muffin.”
Donkey paced, hooves clicking on the rotten wood. “Okay, okay, okay! So, Puss found it in Duloc. Lord Farquaad’s old panic room. It’s a memory. But not a dream, Shrek. A file. Your whole life—the first draft—crammed onto this little wafer.”
“Eight megabytes,” Shrek muttered, turning the disk over. “That’s all they thought I was worth.”
“It’s not a size thing, big guy! It’s a compression thing. Before you were… you. Before the layers, the wisecracks, the swamp karaoke. You were this.” Donkey pointed a fuzzy hoof at the disk’s label. Handwritten in faded marker: SHREK_v1.FINAL.FINAL(2).8MB
“The ogre they didn’t have room for,” Shrek whispered.
A tiny meow came from the catgut. Puss in Boots landed on the railing, holding a small, humming device. “I have acquired the reader, Señor. From the Magic Mirror’s estate sale. It runs on three AAA batteries and a crushed dream.”
Shrek took the device. It was a translucent purple brick with a monochrome green screen. He slid the disk in. The swamp fell silent. Even the leeches stopped leeching.
The screen flickered.
>LOAD SHREK.EXE
Then, words appeared. Rough. Blocky. No voices—just text scrolling like a dying terminal.
>SHREK: (burps) >FIONA: You are not my true love. >SHREK: Okay. (leaves) >THE END.
Shrek stared. “That’s it?”
Donkey squinted. “Wait, keep scrolling.”
>DELETED SCENES – RECOVERED
A second file unfolded.
>SHREK: I like eating slugs alone. >FIONA: I like eating gold slugs. We have nothing in common. >DRAGON: (eats both) >FARQUAAD WINS. KINGDOM BECOMES A STRIP MALL.
>SCENE 14 – ALTERNATE ENDING >SHREK: I am mean and green and that is my entire personality. >DONKEY: Why do you talk like that? >SHREK: Because the writers only had 8MB. Goodbye.
The screen went dark. Then, one last line:
>ERROR: CHARACTER DEPTH NOT FOUND. INSUFFICIENT MEMORY FOR SOUL.
A cold breeze swept the swamp. Shrek slowly removed the disk. He held it between his thumb and forefinger, then snapped it clean in half.
“What are you doing?!” Donkey yelped.
Shrek stood up. He looked at his home—the muddy water, the out-of-tune wind chimes made of old spoons, the “No Humans, No Knights, No Existential Crises” sign.
“They wanted the simple version,” Shrek said, voice low. “The angry burping tub of lard who learns one lesson and rolls credits. No second thoughts. No middle-of-the-night why-am-I-like-this conversations with a talking donkey. No layers.”
He tossed the broken halves into the swamp. A tentacle rose, grabbed them, and sank.
“But I got layers, Donkey. I got parfaits. I got the fear of being hated, and the exhaustion of pretending I don’t care. I got a wife who can belch the national anthem and a friend who never learned when to shut up.”
He turned. For the first time, his eyes weren’t tired. They were heavy.
“That 8MB ogre? He’s dead. I ate him for breakfast and used his bones as toothpicks. Now I take up 80 gigabytes and I’m still not done loading.”
Donkey blinked. Then he burst out laughing. “That’s my guy! Compress this, Farquaad!” shrek 8mb
Puss sheathed his sword. “A profound meditation on data loss and the irreducible complexity of self. Also, I farted.”
Shrek grinned. A real one. “Let’s go eat some waffles. The kind with the little butter packets that never melt right.”
They walked into the shack. The swamp bubbled. Somewhere, deep in the mud, a single pixel of the old Shrek glitched once—then went dark forever.
END
The project is often used as a "stress test" for modern video codecs like AV1 and VP9 to see how much visual data can be preserved at extremely low bitrates—typically around 6-8 kilobits per second. Key Details of the "Shrek 8MB" Post
The Goal: To make the file small enough to be shared as a single attachment on platforms with strict size limits, most notably Discord (which historically had an 8MB limit for free users).
Visual Quality: The resulting video is heavily pixelated, often described as "blobs of color moving," though viewers who know the film well can still "watch" it by mentally filling in the details. Codecs Used:
AV1 (SVT-AV1, rav1e): Often cited for its ability to keep the image "smooth" even when detail is lost.
VP9: A common alternative that provides recognizable shapes at these ultra-low bitrates.
Community Hubs: These encodes are frequently posted on subreddits like r/AV1 or r/DataHoarder as demonstrations of compression efficiency.
For comparison, a standard 4K UHD Blu-ray version of Shrek typically uses about 65,000 MB (65 GB) of data—roughly 8,000 times the size of the 8MB version.
The "Shrek 8MB" phenomenon involves compressing the 90-minute film to fit within Discord's 8MB upload limit for non-Nitro users, resulting in extreme video encoding and heavy pixelation. Achieved through AV1 codec, ultra-low bitrates, and low resolution, this technical feat transforms the movie into a meme-worthy, abstract visual experience. Learn more about the technical details on Reddit.
The "Shrek 8MB" project is a viral internet phenomenon and technical challenge focused on compressing the full 90-minute movie Shrek into a file size of just 8 megabytes. Originally popularized to fit within Discord's former free-tier file upload limit, it has since evolved into a benchmark for video encoding hobbyists. The Technical Challenge
Compressing a feature-length film to 8MB requires an extreme reduction in data, often resulting in a bit rate of roughly 12 kbps—lower than many dial-up internet speeds. Enthusiasts use advanced codecs and creative tricks to achieve this:
Codecs: While earlier versions used H.264, modern attempts prioritize AV1 (AOMedia Video 1), an open-source codec known for superior efficiency at ultra-low bit rates.
Resolution Downscaling: To maintain any level of watchability, the video resolution is typically dropped to 144p or even 72p.
Audio Optimization: Audio often takes up more space than the video. Encoders frequently use Opus or AMR at extremely low bit rates (e.g., 6–10 kbps) or switch to mono audio to save every kilobyte.
Format Tricks: Some creators use tools like MKVToolNix and MKclean to strip unnecessary metadata and optimize the container overhead. Why Shrek?
The choice of Shrek is largely due to its status as an "internet king." The Shrek fandom has turned the movie into a central pillar of meme culture, making it the default subject for absurd technical experiments. The Resulting Experience Watching Shrek at 8MB is often described as "abstract art."
Visuals: Heavy pixelation and "blockiness" make characters difficult to distinguish unless they are close to the camera. The "Shrek 8MB" phenomenon is a legendary internet
Audio: Voices often sound robotic or muffled, similar to a low-quality walkie-talkie.
Cultural Impact: Despite the poor quality, the "8MB Shrek" file became a legendary "copypasta" on Discord, allowing users to share the entire movie as a single, playable attachment. Other "8MB Shrek" References
While the video compression project is the most famous, the term also appears in other niches:
Pinball Maintenance: The Stern Shrek Pinball machine uses 8MB EPROM chips for game data and sound storage.
Retro Computing: Some hobbyists have developed hardware projects like the SHREK (Shift Register Exploration Kit) for educational microprocessing.
Note: The following article is based on the prompt "Shrek 8mb." In the context of internet culture and video editing, this phrase almost universally refers to the legendary "Shrek 8MB" video compression meme, where the entire movie is compressed into a tiny file size. This article explores that phenomenon.
Need the file or want to make one?
- Finding it: Search for "Shrek 8MB" on archive.org, Reddit, or Telegram meme channels (but beware of malware).
- Making it yourself with ffmpeg:
Then adjust encoding to hit exactly 8 MB.ffmpeg -i shrek_full.mp4 -vf scale=64:36 -r 6 -b:v 30k -b:a 8k -ac 1 shrek_8mb.mp4
What Actually Was "Shrek 8MB"?
Let’s be clear: This was not the movie. Not really.
The "Shrek 8MB" circulating on IRC channels (Undernet #warez, anyone?) and LimeWire was technically the full film, but rendered at a resolution of approximately 160x120 pixels. The frame rate hovered between 6 and 10 frames per second (film standard is 24fps). The audio was a 11kHz mono track that sounded like the ogre was gargling gravel underwater.
But the file name was honest. It was exactly 8,388,608 bytes.
Using the cutting-edge (for the time) RealMedia or DivX 3.11 alpha codecs, pirates achieved what seemed impossible. They stripped every non-essential visual element. The opening DreamWorks kid fishing? Reduced to a blurry smear of moon and line. Donkey’s fur texture? Gone. The castle of Duloc? A collection of beige squares.
The result was a file that ran for 90 minutes, fit on a single floppy disk (remember those? 1.44MB? You’d need six, but still), and was just barely recognizable as the film you paid to see in theaters.
How to Spot a Fake vs. The Real Deal
If you’re hunting for shrek 8mb, here are the documented markers of authenticity (per 2channel archives from 2004):
| Feature | Real (2003) | Fake (modern) | |---------|-------------|----------------| | File size | Exactly 8,388,608 bytes (8MB) | 8.1MB or 7.9MB | | Resolution | 240x180, 4:3 | Wider or HD upscale | | Shrek color | Puke green with a brown vest | Standard movie green | | Audio glitch | A pop/crackle at second 4 | Clean loop | | Hidden text | Contains ASCII "DWANGO" in footer | None |
The Dwango Connection
To understand shrek 8mb, we must travel to early 2000s Japan and a now-defunct service called Dwango. Before it became a live-streaming giant (and later merged with Nico Nico Douga), Dwango was a pioneer in mobile and PC animation distribution. It hosted thousands of user-uploaded Flash animations, many of which were bizarre, copyrighted, and gloriously illegal.
Dwango had a peculiar culture: "byte-sized" humor. Uploaders would limit file sizes to absurdly specific numbers—6MB, 12MB, but most famously, 8MB—as a form of anti-piracy joke. The idea was: "I'm not giving you the whole movie. I'm giving you the essence of the movie in 8 brutal megabytes."
The original shrek 8mb is believed to have been uploaded by a user named kuso_oni (roughly "crappy demon") in late 2003. The description, translated from Japanese, allegedly read: "You don't need the rest. This is the whole story. 8MB. Ogre dance."
The Viewing Experience
Let’s set the scene: You have just spent 45 minutes downloading "shrek_8mb_final_real_fixed.exe" from a shady Geocities page. You double-click. RealPlayer opens.
What you see is a masterpiece of abstraction.
- Shrek is a dark green rectangle with two white pixels for eyes.
- Donkey is a vibrating brown smear that moves at double speed due to dropped frames.
- Lord Farquaad is indistinguishable from the vertical beams of his castle.
- The iconic "Welcome to Duloc" song sounds like it was recorded inside a tin can thrown down a flight of stairs.
And yet, you watch the entire thing. You laugh at the "ogre has layers" speech, even though the audio desyncs by four seconds halfway through. Why? Because you didn't have to wait. It was instant gratification. "Shrek 8MB" was the fast food of cinema—nutritionally worthless, but deeply satisfying to a bandwidth-starved teenager.
