Peep the chick mascot

The file browser for
the AI generation.

Your OS shows you filenames. OpenPeep gives every file its own app.

AI generates 30 files. You preview them one at a time.

Your JSON config is a wall of text. It could be an editor.

Quick Look can’t show you what matters. Context can.

Every project folder is just… a folder.

Every file type deserves its own app.

Peeps are mini-applications that live inside your file browser. They don't just preview files — they understand them.

Your OS
With a Peep

poll-config.json

poll-config.json
{
"type": "poll",
"question": "Which iPhone are you most excited about?",
"options": [
{"text": "iPhone 17 Air",
"image": "assets/ip17-air.png"},
// ... 3 more options
]
}
VS

poll-config.json

📊
Poll Studio
4 optionsverified

Which iPhone are you most excited about?

34%
iPhone 17 Air
28%
iPhone 17 Pro
25%
iPhone Fold
13%
iPhone SE 4

episode/

Finder
📁 scripts/
📁 assets/
📁 exports/
📄 episode.json
📄 notes.md
📄 thumbnail-v2.png
VS

episode/

🎬
Episode Planner
In Progress

Script

342 words

Assets

+3

Exports

final.mp4
thumb.png
captions.srt

schedule.json

schedule.json
[{
"date": "2026-03-10",
"title": "iPhone Fold Review",
"status": "filming"
}, {
// ... 12 more entries
]
VS

schedule.json

📅
Schedule View
March 2026
M
T
W
T
F
S
S
Fold
Poll
Air
Edit

Not plugins. Workflow apps.

A Peep can view, edit, generate, validate, and claim entire project folders. Here's what that looks like.

ViewEditToolsVerifyBundle

Poll Studio

A JSON config becomes a visual editor.

  • Content matching recognizes {"type": "poll"} — not just the file extension
  • Visual editor with live preview replaces raw JSON editing
  • Click "Generate" → server-side tool creates 1080×1080 images
  • Verify checks option count, caption length, image dimensions before export
  • One config file. One Peep. An entire creative workflow.

Episode Planner

A folder becomes a production dashboard.

  • Bundle matching claims folders with episode.json + scripts/ + assets/
  • See your script, assets, and exports in one unified view
  • No more digging through nested folders to find what you need
  • The folder IS the app. The Peep IS the workflow.

Your Custom DSL

Any JSON schema. Your own mini-app.

  • Define a custom JSON format for your team’s workflow
  • Build a Peep that renders it as a purpose-built UI
  • Content matching inspects JSON fields to auto-detect your format
  • Ship it on PeepHub. Now everyone on your team has the same tool.
  • This is what "extensible" actually means.

PeepHub: An app store for your files.

Every Peep on PeepHub is a new superpower. Install one, and your file browser learns a new trick.

CSV Analyzer

Interactive data tables with charts

Diagram Editor

Visual flowcharts from .dot files

PDF Annotator

Highlight, comment, extract

API Tester

Run endpoints from .http files

Storyboard Viewer

Visual story layouts from markdown

Config Dashboard

Unified view for .env, .yaml, .toml

Anyone can publish a Peep. If you can write HTML, you can ship a workflow.

Coming Soon

The basics are covered.

OpenPeep ships with Peeps for the file types you use every day. The interesting ones come from PeepHub — or from you.

Image Viewer

.png, .jpg, .gif, .webp, .svg

Video Player

.mp4, .mov, .webm, .m4v

Markdown Editor

.md, .markdown, .mdx

Text Editor

.js, .ts, .py, .css, .sh

JSON Editor

.json

HTML Preview

.html

Peep builder mascot

Build a Peep in an afternoon.

HTML, CSS, and a JSON manifest. Five capabilities. Infinite workflows.

👁 View✏️ Edit🔨 Tools Verify📦 Bundle
peep.json
{
  "id": "my-peep",
  "name": "My Custom Peep",
  "version": "1.0.0",
  "entry": "index.html",
  "capabilities": ["view", "edit"],
  "matches": {
    "extensions": [".custom"]
  }
}

Content matching. Bundle detection. Server-side tools. Structured validation. It's all in the manifest.

Read the Peep Dev Guide