PDO File Documentation
Summary
A PDO (Pepakura Designer Document) file is a papercraft pattern: it unfolds a 3D model into flat, numbered pieces you print, cut, fold and glue into a paper model, popular for cosplay armour and props. It is a proprietary Tama Software binary format, MIME type application/octet-stream. Open and print a .pdo free with Pepakura Viewer (Windows); editing needs the paid Pepakura Designer. There is no reliable third-party reader, so for Mac or Linux ask for a PDF export.
Technical details
| Feature | Value |
|---|---|
| Full name | Pepakura Designer Document |
| File extension | .pdo |
| MIME type | application/octet-stream |
| Format type | Papercraft model — unfolded 3D mesh with printable 2D pattern (binary) |
| Developer | Tama Software (Japan) |
| Application | Pepakura Designer / Pepakura Viewer |
| Introduced | Early 2000s; Designer 6.x current through 2026 |
| Open standard | No — proprietary, undocumented layout |
| Stores | Original 3D mesh + 2D unfold layout, fold/cut/tab lines, textures |
| 3D imports (Designer) | OBJ, STL, 3DS, DXF, LWO, SKP, KMZ |
| Exports (Designer) | PDF, OBJ, STL, SVG (with cutting-machine registration marks) |
| Free viewer | Pepakura Viewer (Windows) — view and print only |
| Magic number | None publicly documented (proprietary version header) |
| Typical use | Cosplay armour, props, paper figures (pepakura papercraft) |
| Related extensions | .obj, .stl, .pdf, .dxf |
| Specification | pepakura.tamasoft.co.jp (no public byte-level spec) |
What is a PDO file?
PDO is the native document format of Pepakura Designer, a Japanese program by Tama Software that is still actively developed (the 6.x line shipped updates into 2026). “Pepakura,” from the Japanese word for papercraft, is the craft of building 3D objects out of folded paper. Pepakura Designer takes a 3D model and automatically unfolds its surface into flat 2D polygons laid out on printable pages, complete with fold lines, cut lines, numbered edges and glue tabs, so the pieces can be reassembled into the original shape. A .pdo stores both the source 3D mesh and that 2D unfold layout together.
The format is enormously popular in the cosplay and prop-making community. Thousands of templates — Iron Man helmets, game armour, Pokémon figures — circulate as .pdo files. Most hobbyists only need to view and print one, which is exactly what the free Pepakura Viewer does. The catch, and the reason for most PDO questions, is that the format is proprietary and undocumented, with essentially no reliable third-party reader, so your options are Tama Software’s own tools or a PDF export made from them.
The unfold: from 3D mesh to flat printable pieces
The core idea a .pdo captures is the unfold (mathematically, an edge-cut unfolding of a polygon mesh). A closed 3D surface cannot be flattened onto paper without cutting it along some edges. Pepakura Designer chooses a set of cut edges and rotates each connected group of faces down into a single flat plane, producing a 2D pattern whose pieces, when cut out and folded back along the shared edges, recreate the 3D form.
Workflow the .pdo represents:
3D model (OBJ/STL/3DS…) → choose cut edges → flatten faces to 2D
→ arrange pieces on pages → add fold/cut lines, numbered tabs
→ print on cardstock → cut, fold, glue → finished paper model
Every edge in the flattened pattern is classified. Cut lines are where you separate pieces with a knife; mountain and valley fold lines (drawn differently) tell you which way to crease; and numbered glue tabs mark which edge joins which, so a piece labelled 14 connects to the other edge labelled 14 elsewhere on the sheet. This edge numbering is the assembly instruction baked into the pattern, and it is what turns a confusing sheet of polygons into something buildable.
What a PDO holds
Because Tama Software has never published a byte-level specification, the honest description of a .pdo is by content rather than by offset. The file begins with a version/header block that Pepakura’s own parser reads, and there is no stable public magic signature to identify it by; recognition is by extension and by the program that opens it. It is a binary file, not text.
PDO contents
├─ 3D mesh data the original imported model geometry
├─ 2D unfold layout the flattened polygons arranged across printable pages
├─ Fold / cut / tab mountain & valley fold lines, cut outlines, numbered flaps
├─ Textures / materials optional surface textures shown on the pieces
└─ Assembly metadata edge numbering and connection info for reassembly
Keeping both the 3D mesh and the 2D layout in one file is what lets the Viewer show a live 3D preview beside the flat pattern and highlight, when you click a 2D piece, exactly where it sits on the model. That cross-reference is the practical value of the format over a plain printed pattern: you can see what you are building as you build it.
Opening and printing: free Viewer versus paid Designer
There are two Tama Software programs, and picking the right one is the whole practical question. The free Pepakura Viewer (Windows) opens any .pdo, lets you rotate the 3D model, highlights how pieces connect, and prints the 2D pattern onto cardstock. It cannot edit, rescale or unfold anything — but for the common case of printing a template someone else made, that is all you need. The paid Pepakura Designer is required to create patterns: import a 3D model, unfold it, rescale it (important for cosplay, where you fit armour to your body), edit the layout, and export.
Neither program has a native Mac or Linux build. Non-Windows users run the Viewer or Designer under Wine, CrossOver, or a Windows VM such as Parallels — or, more simply, ask the template’s creator for a PDF export of the pattern, which opens on any device. Download the tools only from Tama Software’s official site; the .pdo itself is passive data with no executable code, so the only real safety concern is avoiding “free download” portals that wrap the installer in adware.
Exports: PDF for printing, OBJ/STL for 3D, SVG for cutting machines
Pepakura Designer exports several formats, each for a different purpose, and it helps to know what each one actually contains.
PDO → PDF the printable 2D pattern; shareable, opens anywhere (best for Mac/Linux
or a copy shop). The free Viewer can reach this via Print → "Print to PDF".
PDO → OBJ the underlying 3D MESH, not the unfold. Designer only.
PDO → STL the model geometry for 3D printing, again the solid model not the pattern.
PDO → SVG the 2D pattern with registration marks for cutting machines
(Silhouette CAMEO, Cricut) so pieces are auto-cut instead of by hand.
The distinction that trips people up: exporting to OBJ or STL gives you the 3D model, not the flattened papercraft layout, so it is useful for 3D printing but not for paper building. The PDF export is the one that carries the actual printable pattern, which is why “PDO to PDF” is the conversion most makers want. The newer SVG export with registration marks is a genuinely modern touch for people who cut pieces on a Silhouette or Cricut rather than by hand.
Frequently asked questions
How do I open a PDO file for free?
Use Pepakura Viewer (free, Windows) from Tama Software. It opens any .pdo, shows the 3D model, highlights how the pieces connect, and prints the flat pattern onto cardstock. It cannot edit or unfold — for that you need the paid Pepakura Designer — but for printing a downloaded template the Viewer is enough.
How do I open a PDO on Mac or Linux?
There is no native Mac or Linux build. Run the Windows Pepakura Viewer or Designer through Wine, CrossOver or a Windows VM (Parallels), or ask the template’s creator for a PDF export, which opens on any device. No reliable third-party PDO reader exists.
Can I print a PDO without Pepakura Designer?
Yes. The free Pepakura Viewer prints the pattern. You only need the paid Designer if you want to edit, rescale, or create your own unfolds. To get a shareable file, use the Viewer’s Print → “Microsoft Print to PDF”.
References
- Tama Software — Pepakura Designer (official)
- Tama Software — Pepakura Viewer (free) download
- Pepakura Designer — release notes / version history
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.