Bring back the big box era of PC gaming with GOG's printable templates

The digital distribution era erased the physical shelf. For nearly two decades, buying a PC game meant a small download, a license key. And an empty space on your shelf. But GOG's recent move to bring back "big box" PC games-complete with printable templates and downloadable 3D models-isn't just a nostalgic gimmick. It's a case study in how software platforms can preserve the experience of physical media, not just the code. GOG (formerly Good Old Games) has always positioned itself as a DRM-free haven for classic titles. This new preservation push, first reported by Ars Technica, extends that mission toward the tangible artifacts that once surrounded software: the cardboard box, the printed manual, the feelies. And even the registration cards. For engineers, the interesting question isn't "Why would anyone print a box? " but rather "How do you design a system that lets a distributed community reproduce physical objects with high fidelity, open formats,? And no central manufacturing pipeline? " That's a problem in digital twins, reproducible builds, and asset versioning. GOG's printable templates and 3D models are more than a marketing novelty. They represent a pragmatic approach to digital preservation that borrows from open-source tooling, code archaeology. And distributed caching. In this article, I'll break down the engineering choices behind the initiative, explore how it fits into established archival frameworks, and show what production teams can learn from it when building their own preservation or nostalgia-driven features. ## Why Physical Game Packaging Matters in a Digital Era Physical packaging was never just a container. It was a data delivery mechanism with a defined set of constraints: size, weight, durability. And information density. The old "big box" PC game format-roughly 9. And 5 x 115 inches-evolved to hold floppy disks or CDs. But it also carried critical metadata. Manuals included system requirements, installation instructions, keyboard reference cards, and sometimes technical appendices that software vendors never shipped as separate files. When we moved to digital distribution, that metadata fragmented or disappeared entirely. From a software engineering perspective, the Loss Of Physical packaging is a documentation gap. Modern game launchers may include a PDF manual or a wiki link, but they rarely replicate the hierarchical layout of a printed reference card. GOG's printable templates aim to fill that gap by providing high-resolution scans and vectorized layouts that preserve the original typography, color profiles. And even the box folds. This is analogous to how developers use reproducible build manifests to ensure a binary can be rebuilt from source; here, the "source" is the original print artwork. The market size for retro game collecting also plays a role. According to data from PriceCharting and eBay analytics, sealed retro PC games have appreciated by over 300% since 2015. But original boxes are scarce, fragile, and expensive. A printable template democratizes ownership: anyone with a decent inkjet printer and 160gsm cardstock can create a shelf-ready replica. That's not counterfeit; it's a form of backup for physical provenance. GOG is effectively offering a highly compressed, open-source format for a physical object. ## GOG's Preservation Strategy: More Than Just ROM Files GOG has built its business on delivering old games that actually run on modern Windows, Linux, and macOS. That often requires reverse engineering, custom wrappers (DOSBox, ScummVM), and patching. But until now, the preservation focus was entirely on executable code and necessary data files. The "big box" initiative extends that scope to the cultural baggage around the software. Think of it as the difference between archiving a source code repository and archiving the entire Release process, including marketing collateral. In archive science, the CCSDS 650. But 0-B-1 (OAIS) reference model defines an Information Package as containing not just the content data object but also representation information that makes the object understandable. A big box manual is representation information: it tells you how to play, what the story is. And even what the developer thought you needed to know. Without it, a game binary is just a sequence of instructions. GOG's approach of distributing templates and 3D models as downloadable files is technically straightforward-probably just a set of ZIP archives alongside the game installer. But the curation effort is significant. Each template must be scanned from a high-quality original, restored to remove wear, color-corrected against standard ICC profiles. And then exported as a print-ready PDF or SVG. For 3D models, the original box must be either photogrammetrically scanned or manually modeled. That's not a script anyone can run overnight; it's a manual pipeline requiring domain expertise. ## The Engineering Challenge of Recreating Box Art Accurately Accurate box art reproduction is a computer vision and color science problem. Original cardboard boxes used spot colors (Pantone), offset printing. And sometimes metallic inks or embossing. A flatbed scanner captures a 2D projection - but lighting, scanner gamma, and paper texture introduce noise. GOG's templates likely go through a multi-step restoration process: first, a high-DPI scan (600-1200 DPI), then geometric correction using corner detection, then color calibration against a known target (e g., an IT8. And 7/2 target)I've worked on similar projects digitizing technical manuals. And the difference between a raw scan and a restored vector file is often a day of manual work per page. For printable templates, the output format matters. A raster PDF is easy to generate but scales poorly; a vector PDF or SVG preserves text as outlines and allows infinite scaling. The tradeoff is file size and complexity. GOG appears to favor PDFs with embedded vector data for fold lines and margins-a format that works well with `pdfjam`, `qpdf`, and other command-line PDF tools. If you want to fork a template and change dimensions, vector formats are the only practical choice. Color fidelity is Another challenge. Home inkjet printers use CMYK or extended gamut inks, but original boxes were printed with Pantone solid colors. Converting Pantone to CMYK is lossy. A high-end RIP (raster image processor) can drive a printer with ICC profiles. But most consumers will just hit "Print" and accept the result. GOG can't control that final step, but it can provide pre-converted print-ready files with embedded profiles. Which is what professional print shops expect. The engineering choice is to standardize on ISO-coated v2 (FOGRA39) for CMYK and leave RGB for screen viewing-exactly the kind of decision that makes or breaks a community-driven reproduction effort. ## Printable Templates as Open-Source Documentation Artifacts A printable template is essentially a declarative specification for a physical object. It defines dimensions, folds, bleed areas, and artwork placement. In that sense, it's analogous to a Dockerfile: a set of instructions that, when executed in a predictable environment (a printer with the right paper), produces a consistent artifact. The difference is that a Docker build is deterministic. While a home print job is not-but the template still reduces variability significantly. This approach borrows from the reproducible builds movement in software. Projects like Debian's reproducible builds aim to ensure that a given source tarball always produces an identical binary. For physical boxes, reproducibility means that two people on different continents, using the same PDF and same paper weight, get visually similar results. GOG can't guarantee exact color matches. But the geometric layout-the fold lines, the glue tabs, the spine width-can be specified to sub-millimeter precision in SVG. That's the kind of rigor that made open-source hardware projects like Arduino successful: clear, verifiable specifications. One underappreciated aspect is version control for templates. If a restoration error is found, how do you push an update? GOG could host the templates in a Git repository, but its current model appears to be ZIP downloads tied to the game purchase. That's fine for one-off use, but it limits community collaboration. A better long-term approach would be to expose the templates as a public Git repo (with appropriate licensing) so that users can fork, fix. And submit pull requests. The Internet Archive already does something similar for scanned books; GOG could learn from that. ## 3D Models and the Rise of Digital Twins for Retro Hardware The downloadable 3D models are the most intriguing part of GOG's announcement. A 3D model of a big box game is not just a visual gimmick; it's a digital twin of a physical artifact that no longer exists for most players. You can load the model into a game engine, a VR environment, or a 3D printer slicing tool and inspect its geometry. That's useful for collectors who want to verify dimensions before building a shelf. But it also opens the door to virtual museums. Creating accurate 3D models of cardboard boxes is a photo-grammetry problem. You need multiple images from different angles, good diffuse lighting. And a scale reference. Tools like Meshroom (open-source) or RealityCapture (commercial) can generate a mesh from images. But the resulting model often has texture warping at edges. A more reliable approach is manual modeling in Blender using the box's known dimensions and applying the scanned artwork as a UV-mapped texture. GOG likely used the latter because cardboard boxes are simple rectangular prisms with well-defined folds-easy to model parametrically. The file format matters here. STL is the de facto standard for 3D printing. But it lacks color and texture. GLB (binary glTF) is better for interactive viewing because it bundles geometry, textures,, and and materials in one fileIf GOG is distributing models for "desktop perusal," they probably use GLB. For engineers, that's a smart choice: glTF is an open standard maintained by Khronos Group, and it's supported by three js, Babylon js, and most game engines. You can drop a GLB into a web viewer with a single `` element, a topic I've covered related article: building lightweight 3D viewers for web. ## How CDN and Edge Caching Support Preservation Assets Distributing hundreds of megabytes of scanned templates and 3D models is a content delivery problem. GOG already operates a global CDN for game installers. So adding preservation assets is technically trivial-but the access patterns differ. Game installers are large, rarely-accessed files; templates and 3D models are small, often-downloaded-once files that may be requested by many users simultaneously after a news release. That's a classic cache stampede scenario. In my production work with AWS CloudFront and Fastly, I've found that small, popular assets benefit from aggressive edge caching with long TTLs, plus a `Cache-Control: public, max-age=86400, immutable` header if the content is versioned. GOG could use content-addressed URLs (e, and g, `/templates/game123/box-front-v2. pdf`) so that when a template is updated, the URL changes and the cache is automatically invalidated. This is exactly how Docker registries and npm work. If GOG isn't already doing this, they should-it reduces origin load and improves download latency. A more subtle issue is bandwidth cost. A high-resolution 600 DPI box scan can be 200 MB as a TIFF. GOG probably compresses to JPEG or PNG in the PDF. But users may still pull 50-100 MB per template. Multiply that by tens of thousands of nostalgic users, and bandwidth becomes real money. Using a CDN with tiered caching and Brotli compression for text-based assets (SVG) can cut transfer sizes significantly. For 3D models, Draco compression can reduce GLB file sizes by 80% or more, at the cost of decode time on the client. GOG would do well to provide both compressed and uncompressed versions, letting power users choose. ## Licensing, Copyright. And the Legal Mechanics of Preservation Providing printable templates raises thorny legal questions. The artwork on a big box is copyrighted. But GOG holds distribution rights for most games it sells. However, the template itself-the layout, fold lines. And dimension specifications-is a new work that GOG can license separately. Many open-source projects use Creative Commons licenses for such things, but GOG hasn't yet clarified the license for its templates. Without a clear license, users can't legally modify or redistribute the templates. Which severely limits the "preservation" aspect. From a compliance engineering standpoint, the right approach is to attach a permissive license like CC BY-SA 4. 0 to the template files. While keeping the embedded artwork under the original game's copyright. This is similar to how open-source hardware projects separate the PCB design (open) from the component footprints (often proprietary). The template becomes a document format standard, while the artwork it carries remains protected. GOG could even provide an SVG template with placeholder boxes so users can create their own "big box" style packaging for non-GOG games. There's also a question of trademark. The "GOG Galaxy" logo and the company's name are trademarks. If a user prints a template and sells the resulting box, that's infringement. But GOG has so far been lenient with fan projects. And the initiative seems aimed at personal use. For enterprise software teams, this is a reminder that digital preservation always includes a legal component: you can archive the bits. But you must also preserve the rights metadata-something that the METS (Metadata Encoding