Extracting Postman v12 Collections Offline: Reverse-Engineering LevelDB and Building an OpenAPI Porter

kiliankaena85-byte — Tue, 06 Oct 2026 05:33:05 +0000

Why We Built This

Postman recently deprecated the offline Scratch Pad and mandated cloud synchronization. For developers working with sensitive microservices, financial APIs, or enterprise environments, syncing API collections to third-party clouds is a serious compliance and security risk.

While migrating to open-source alternatives like Bruno or Insomnia is ideal, Postman v12 stores collections in a proprietary modular .request.yaml format backed by Chromium LevelDB partitions (IndexedDB/https_desktop.postman.com_0.indexeddb.leveldb).

How It Works

We reverse-engineered Postman's local desktop storage to create Postman Vault:

LevelDB Discovery: Parses Chromium LevelDB logs and write-ahead logs in %APPDATA%/Postman to uncover all local collection workspaces and environment registries.
Modular Parser: Traverses Postman v12 .request.yaml hierarchies, reconstituting folders, scripts, and parameter definitions.
Universal Converter: Emits both standard Postman Collection v2.1.0 JSON (1-click import into Bruno/Insomnia) and OpenAPI 3.0.3 YAML/JSON specifications.
Security Sanitizer: Automatically scrubs production JWT tokens, private authorization headers, and credentials before Git commits.

Try It Locally (Zero Cloud, 100% Offline):

git clone https://github.com/kiliankaena85-byte/postman-vault.git
cd postman-vault
npm install
node bin/cli.js ui

This launches the local web dashboard at http://127.0.0.1:4567 for 1-click inspection and exporting.

GitHub Repository: https://github.com/kiliankaena85-byte/postman-vault

We'd love your feedback, feature requests, and stars on GitHub!

DEV Community: kiliankaena85-byte

Extracting Postman v12 Collections Offline: Reverse-Engineering LevelDB and Building an OpenAPI Porter

Why We Built This

How It Works

Try It Locally (Zero Cloud, 100% Offline):