PK3 to GLB Converter
FileFlip converts PK3 to GLB entirely inside your browser, using Assimp compiled to WebAssembly. The file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. That means no file-size limit, no queue and no account.
How do I convert a PK3 file to GLB?#
- Drop your PK3 file onto the converter at the top of this page, or click it to pick one from your computer. You can add as many as you like.
- Leave the target set to GLB and the conversion starts on its own. FileFlip downloads 11.2 MB of WebAssembly the first time and nothing after that, then runs Assimp on your own machine.
- Save the GLB file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting PK3 to GLB lose quality?#
Not in the sense of pixels or samples. Converting PK3 to GLB rebuilds the file in GLB's own model rather than re-encoding it, so everything GLB can represent comes through exactly and anything it cannot has to be dropped. Expect the geometry to be exact, and anything the target has no place for, such as a rig, to be left behind.
Is it safe to convert PK3 files online?#
Yes, because nothing is uploaded. FileFlip converts PK3 files inside the browser tab you already have open, using WebAssembly builds of the same engines a desktop converter would install. Your file is read from your own disk into the page's memory, and no request carrying it is ever made.
You do not have to take that on trust. Open your browser's network panel, run a conversion, and you will see the engine come down and your file go nowhere. There is no upload, no server-side copy, no retention window, and no account tied to what you converted.
How FileFlip works lists every engine, its version and its download size, and shows how to check for yourself that nothing leaves your machine.
What PK3 to GLB actually does to the file#
Converting PK3 to GLB runs on Assimp, downloads 11.2 MB of WebAssembly the first time and nothing after that, rebuilds the file in the target's own model.
| Engine | Assimp |
|---|---|
| Conversion path | One step: PK3 → GLB |
| Downloaded to your browser | 11.2 MB, once, then cached by your browser |
| Quality | Rebuilt in the target's model |
| You get back | One file |
| Where it runs | In a background worker, so the page stays responsive |
What survives the conversion
| What is in the file | This conversion | Why |
|---|---|---|
| Materials | Sometimes | Survives for some files and not others. |
| Textures | Sometimes | Survives for some files and not others. |
| Skeleton and animation | Sometimes | Survives for some files and not others. |
What is a PK3 file?#
A PK3 file is a Quake III Arena game archive, an ordinary ZIP file renamed with a .pk3 extension so id Tech 3's engine loads its maps, models, textures and sounds straight out of the package.
Use PK3 to package and distribute a Quake III Arena map or mod's assets as one file that the engine loads directly.
Convert a PK3 into its individual files when the goal is to reuse a specific model, texture or sound rather than run the package inside the game.
What is a GLB file?#
A GLB file is glTF's binary packaging, developed by the Khronos Group, wrapping the JSON scene description together with its geometry buffers and textures into one self-contained file instead of a JSON document with separate buffer and image files beside it.
Use GLB whenever a model has to be handed to a web viewer, AR app or game engine as a single upload.
Convert GLB back to glTF's JSON form only when something inside the file needs to be read or edited directly.
PK3 to GLB questions people ask#
What is a PK3 file?
A PK3 file is a Quake III Arena game archive, structurally just a ZIP file with the extension changed to .pk3 so id Tech 3's engine recognizes and loads it directly. It typically bundles a mod or map pack's BSP levels, MD3 models, textures and sounds together.
Can I open a PK3 file with a normal ZIP tool?
Yes. A PK3 file is an ordinary ZIP archive under a different extension, so any ZIP tool, or simply renaming the file to end in .zip, opens it and lists its contents.
Why does Quake III use PK3 instead of loose files?
Packing a mod or map's files into a single PK3 keeps them organized in the exact folder structure the engine expects and lets it read straight out of the archive without unpacking to disk first, which made distributing and installing custom content much simpler than shipping loose files.
Can I open a GLB file directly on my phone?
Android's Scene Viewer opens a GLB file straight into an AR view without a separate app, since it's built to consume glTF's binary form directly. iOS's AR Quick Look expects USDZ instead, so a GLB usually needs converting first to view in AR on an iPhone.