File types

Cabinet treats specific file formats as first-class views. Drop them in your cabinet folder and they render inline — markdown, CSV, PDF, mermaid, images, video, audio, code, office docs, embedded apps, and Google Workspace pages all just work.

Click any row in the table for a live or annotated example. Anything not on this list still lives in your cabinet as an asset linked from a markdown page.

Why this matters

A scattered tool stack means you open a different app to view each file. Cabinet collapses that — your screenshot, your spreadsheet, your podcast clip, your codebase, and your meeting notes all sit in the same sidebar, all browsable, all searchable, all editable in place. The agent that reads your launch plan can also see the screenshot you pasted into it.

Patterns

A few rules that show up across all the file-type viewers:

Files render where they live. A pasted screenshot saves into the same folder as the page that holds it. Move the page folder, the assets move with it.

The sidebar shows actual file extensions. No hidden conversion. What you see in ls is what you see in Cabinet.

Read-only is fine — and intentional. Office docs, PDFs, and Google Workspace pages render but don't allow inline edits. Cabinet's editor is for markdown; everything else has a source app.

Sub-pages

• Markdown page — the editor surface itself.
• CSV data — interactive table editor with source view.
• PDF document — inline browser-native viewer.
• Mermaid diagram — rendered live.
• Images — paste, drop, URL, resize handles.
• Video & audio — inline players.
• Source code — syntax-highlighted viewer.
• Office documents — .docx / .xlsx / .pptx, inline.
• Embedded apps — folders with index.html.
• Google Workspace pages — live Sheets / Docs / Slides / Forms.
• Linked content — symlinks and .repo.yaml git repos.

Read on

• Markdown editor — the editing surface itself.
• Reference → File structure — what else lives in a cabinet folder.