Everything you wanted to know but were too afraid to ask your Quadra.
We call these “Frequently Argued Questions” because most of them come from heated debates on vintage computing forums at 2 AM. We appreciate your passion. We share it. That’s why we’re all here.
RetroGate is a macOS proxy server that sits between your vintage computer and the modern internet. It handles TLS encryption, converts HTML5 to HTML 3.2, transcodes modern image formats to JPEG/GIF, and generally performs twenty years of technological regression so your old Mac doesn’t have to.
Think of it as a universal translator between your Macintosh Plus and the year 2026. Except instead of translating Klingon, it translates React components into <table> layouts.
Both! If your vintage Mac or PC can make HTTP requests through a proxy, RetroGate handles the rest. SheepShaver, Basilisk II, QEMU, PCem, 86Box, or genuine beige hardware that has survived the fall of empires, the rise of the iPhone, and at least two office moves — RetroGate loves them all equally.
We don’t discriminate based on age, color depth, or how loud the hard drive sounds.
Because it’s a gate between the retro internet and the modern one. Also because every good project needs a name that sounds vaguely like a political scandal. RetroGate: the controversy of making old computers useful again.
We considered “Proxy McProxyFace” but felt it lacked gravitas.
Yes. RetroGate is a proxy server running on your local network. It’s no different from any other HTTP proxy. The Wayback Machine integration uses the Internet Archive’s public API and respects robots.txt.
The only law you might be breaking is the unwritten one about spending your Saturday night configuring TCP/IP on a Power Macintosh 7200 instead of going outside. We won’t judge.
No. RetroGate is a macOS app built with SwiftUI, SwiftNIO, and CoreGraphics. It requires macOS 13+ and runs natively on both Apple Silicon and Intel as a Universal Binary.
We know this is slightly ironic — a proxy for old computers that requires a not-so-old computer. But SwiftNIO is really fast, CoreGraphics handles image transcoding beautifully, and frankly, your Mac isn’t doing anything else productive while it serves HTML 3.2 to a Quadra.
Yes! Your vintage browser sends a plain HTTP request to RetroGate. RetroGate then makes the HTTPS request on its behalf, using modern TLS 1.3. If the HTTPS connection fails (expired cert, etc.), RetroGate falls back to plain HTTP automatically.
Your Mac OS 9 machine never needs to know about certificate chains, OCSP stapling, or any of that TLS handshake business. It has enough problems.
Because the Wayback Machine’s website is itself a modern web application. It uses JavaScript, modern CSS, HTTPS — none of which your vintage browser supports.
It’s like asking why you can’t read a book through a window — technically the words are there, but there’s a pane of glass (and 25 years of web standards) in the way. RetroGate is the person who opens the window for you.
RetroGate caps responses at 10 MB. In practice, no page from 1999 was anywhere near this limit. In 2026, some JavaScript bundles exceed it. We don’t talk about those.
A typical transcoded page is 10–50 KB. For reference, the original Mac OS 9 installer was 15 MB. You could fit hundreds of transcoded web pages in the space of one operating system. What a time to be alive.
You can certainly try. Sites that are mostly text (Wikipedia, news articles, forums) work great.
Sites that are mostly JavaScript-rendered (Twitter, modern Reddit, Gmail) will give you a blank page
with perhaps a sad <noscript> message.
RetroGate preserves <noscript> content by default, so you’ll at least see
something. Usually it’s a polite suggestion to enable JavaScript, which is
adorably naive given that your browser thinks ECMAScript is a skin condition.
Mac presets output MacRoman. PC presets output ISO-8859-1.
Unicode characters are converted with lossy encoding — curly quotes become straight quotes,
em-dashes become --, ellipses become ..., and trademark symbols become (TM).
If you’re seeing garbled characters, you probably have a Mac preset on a PC browser or vice versa. This is the “you had one job” of character encoding, and it’s been causing problems since 1991.
That’s not RetroGate — that’s the Internet Archive. It serves billions of archived pages from a non-profit’s server room. It’s doing its best with the digital equivalent of duct tape and idealism.
RetroGate helps by caching Wayback responses locally (archived content is immutable, so this is safe) and by prefetching images in parallel. After the first load, subsequent visits should be nearly instant.
Consider donating to the Internet Archive. They’re literally preserving human knowledge. That’s worth a few bucks.
RetroGate has “temporal consistency” built in — when a page loads from a specific snapshot date, all sub-resources (images, CSS) are fetched from that same date. But sometimes the Internet Archive simply didn’t crawl a particular image on that date, and the closest match is from a different year.
The Wayback Timeline tab (Monitor → Wayback Timeline) shows you the actual delta between your target date and each fetched resource. Green means exact match, gold means close, red means the Archive is doing its best with limited data. We live in an imperfect world, and so does time travel.
A capsule is a named collection of cached pages, exported as a single .retrogate-capsule
file. You can bundle up a research binge, a set of Wayback snapshots, or just a pile of sites that
no longer exist, and share the whole thing with another RetroGate user. Import it, and those pages
are instantly available on their Mac too.
It’s a mixtape. For websites. In 2026. We don’t know why either. But we’re committed to it.
Yes — well, partially. Flip on Offline Mode and RetroGate serves already-cached pages straight from disk without touching archive.org or the live web. Cache misses return a local 404 instead of waiting for a network timeout. A gold dot in the sidebar reminds you the world is (gently) walled off.
Perfect for conference demos on flaky Wi-Fi, airplane mode nostalgia sessions, or when rate-limiting archive.org feels impolite. Your PowerBook has been training for this its whole life.
As much as you let it. Set a max size (in MB) and a max age (in days) in the retention policy, and RetroGate evicts the least-recently-used entries first. Pinned entries are never evicted — even if your cache is 100% pinned, nothing gets deleted. At that point it’s your problem, not ours.
The Cache tab shows live stats: entries, on-disk size, hit rate, oldest entry. Clear-all is one button and zero regrets.
Yes. RetroGate ships with SQLite FTS5 full-text search using Porter stemming. Supports phrases, AND/OR/NEAR operators, and prefix wildcards. Build the index once (one button, takes a few seconds), then search across everything you’ve ever cached in milliseconds.
It’s probably faster than the search box on most of the websites you’re archiving. Which says more about modern search boxes than it does about SQLite.
Paste a list of URLs (one per line, # comments allowed, bare hostnames ok) and RetroGate
warms the cache at one request per second. When it finishes, optionally wrap the whole batch into a
capsule for sharing or archival.
One request per second is deliberate. Archive.org is a non-profit. Don’t be the reason they add a rate-limit. Be polite, like a 1999 web crawler with manners.
SheepShaver’s slirp networking is, shall we say, temperamental. If browsing suddenly stops working, restart SheepShaver. This is not a RetroGate bug. This is a SheepShaver feature.
(It’s a bug. It’s definitely a bug. But calling it a feature makes everyone feel better.)
Your host machine is reachable at 10.0.2.2 from inside the VM.
Configure this as your HTTP proxy address with port 8080.
RetroGate strips <applet> tags because they crash SheepShaver’s
MRJ (Mac OS Runtime for Java). This is a known SheepShaver issue, not a RetroGate issue.
QuickTime embeds (<embed> and <object>) are preserved because
QuickTime is eternal and beautiful and works perfectly in SheepShaver. Unlike Java. Because Java.
No. This is infrastructure.
Nostalgia is looking at pictures of old Macs on Instagram (on your iPhone). RetroGate is actually using those old Macs to access the modern internet. There’s a difference between “remember when things were simpler” and “I have made things simpler again with a 3000-line Swift proxy server.”
Also, if nostalgia is wrong, explain why you still have a box of SCSI cables in your closet. Exactly.
Because a Macintosh Plus deserves to browse Wikipedia. Because a PowerBook 520 shouldn’t cry in a landfill just because the web moved on. Because Mac OS 9 — the last truly great Classic Mac OS, fight me — should be able to reach the entire World Wide Web.
But also: because it’s fun. Because seeing a modern website rendered in HTML 3.2 on a CRT is genuinely delightful. Because the internet was better when pages were 12 KB and loaded instantly and didn’t need consent banners for 47 different tracking cookies.
Because some of us remember when the web was fun, and we want it back.
Absolutely! RetroGate is open source under the GPLv3 license. The code is on GitHub. We welcome pull requests, bug reports, feature suggestions, and strongly-worded opinions about whether Mac OS 8 or Mac OS 9 was better.
(It was Mac OS 9. This is not up for debate. The FAQ has spoken.)
So many things:
We have more ideas than any reasonable person should. Send help. Or pull requests. Preferably both.
Got a question we haven’t answered? Send us a message. We promise to read it on a vintage Mac for authenticity.