See storage as data.
Move from origin to DBOPFS application, table, and record without reverse-engineering directory conventions on every visit.
DBOPFS-powered storage workspace
Your DBOPFS data, made legible.
Explore an origin's DBOPFS applications, tables, and records in a focused workspace built for real inspection, editing, previewing, export, and print workflows.
Local browser operation. One-time commercial licensing. No DBOPFS Studio cloud account, monthly subscription, or mandatory recurring license fee is required after purchase. Optional support, future major-version upgrades, and third-party services may have separate costs.
Chromium MV3
ChromeEdgeBraveVivaldiOpera
Tables06
Records248
Storage18 MB
observation-0248.json
{ "title": "Summer survey", "status": "reviewed", "coordinates": { "latitude": 41.8781, "longitude": -87.6298 }, "attachments": 3 }
The 29-second product tour
See DBOPFS Studio in motion.
A quick look at the selected-origin dashboard, record workflow, supported previews, and local-first design.
Read the jingle lyrics and visual summary
Lyrics: D-B-O-P-F-S Studio, bring your data into view. Apps and tables, records too. Local-first and built for you. Open, inspect, edit, preview. See the structure coming through. Your DBOPFS data made legible. D-B-O-P-F-S Studio.
Visuals: The shipped Studio interface connects to a selected origin, summarizes DBOPFS storage, opens and validates a JSON record, previews Markdown and a Chromium PDF workflow, and closes on its local-first design and browser compatibility.
Database semantics first
Not just another file tree.
DBOPFS Studio uses the DBOPFS module as its primary data layer. Application scopes, tables, records, formats, and guarded data operations stay visible throughout the current 0.1 interface.
Work where you inspect.
Open text-based records and files, make focused inline changes, validate structured content, and save through the connected origin.
Know before you change.
Review origin connection, browser-reported storage use, quota, persistence state, and guarded destructive actions from one dashboard.
A practical workspace
From inspection to action.
Use one coherent surface for current DBOPFS workflows without turning the extension into a server, cloud account, or opaque copy of your database.
Dashboard and DBOPFS explorer
Connect the active or inspected origin, review storage health, browse DBOPFS applications, tables, and records, filter names, and inspect record metadata.
Editing and record operations
Create tables and records, import files into a table, export an application, edit and save supported text-based records, and delete records with exact-name confirmation.
Native media and PDF handling
Preview images, audio, and video with native browser controls. Switch between exact source and rendered Markdown or non-destructive formatted JSON and JavaScript views. PDFs open in Chromium's own viewer for viewing and printing.
Local by design
Inspected content stays in the browser unless you intentionally export, download, copy, or print it. No DBOPFS Studio account or analytics service is required. Commercial licenses are one-time purchases for the licensed version, with no monthly subscription or mandatory recurring DBOPFS Studio license fee after purchase.
The browser is the boundary
One connected origin at a time.
OPFS is isolated by protocol, hostname, and port. DBOPFS Studio works through a live active or inspected page that you connect; it cannot expose every closed site's private filesystem as one global drive.
TRUST / EXPLICIT
You choose the workspace target.
The manifest allows an isolated bridge on HTTP(S) pages. DBOPFS operations begin when the Studio sends a request to the selected tab. Connection state is visible, and switching origins does not merge their data.
Roadmap · beyond 0.1
A broader OPFS toolbox comes next.
The current UI focuses on DBOPFS application data. Raw OPFS browsing outside DBOPFS namespaces, plus rename, move, and copy commands, are planned capabilities—not features of the shipped 0.1 interface.
PLANNED / CLEARLY SEPARATE
Raw files without losing DBOPFS context.
The planned raw view will complement the database-aware explorer. Until it ships, use the Studio for the DBOPFS applications, tables, and records displayed by the current interface.
Chromium family
One extension, several browsers.
Chrome and Microsoft Edge are first-class targets. Other current Chromium builds can use the same unpacked Manifest V3 extension when they provide the required APIs; privacy modes, enterprise policies, and native PDF controls may differ.
CChromeFirst-class target
EMicrosoft EdgeFirst-class target
BBraveCompatible target
VVivaldiCompatible target
OOperaCompatible target
Capability detection matters. A Chromium foundation does not make every browser build identical. DBOPFS Studio checks the storage surface it needs and reports unavailable capabilities instead of assuming them.
Ready to inspect differently?
Load DBOPFS Studio from source.
The first build is installed as an unpacked extension from this repository. Store publication will be documented when it is actually available.