01
Make the film
Open the actual São Tomé archive and try to finish the documentary.
HAAM Production Studio
One studio.Four dimensions of making.
Move between image, motion, space, and world publishing from one browser-native production environment. Each editor is focused, private, and aligned with HAAM's local-first browser storage and runtime capability foundation.
Studio principle
Your source files stay under your control.
The tools use browser capabilities for processing, draft storage, runtime checks, local asset staging, and export. Work begins on your device and remains there unless you choose to move it elsewhere.
A product byHAAMStudio floor
Choose your workspace
Each workspace has its own interface and export formats, joined by a common production identity, privacy model, runtime readiness layer, local asset vault, and browser-native storage strategy.
01Image
Photo Editor
Adjust color, crop, rotate, transform, and export photographs locally as JPEG, PNG, or WebP.
- Adjustments and presets
- Crop and transform
- Local image export
02Motion
Video Editor
Trim, reframe, caption, preview, and export video without sending the source file to HAAM servers.
- Trim and reframe
- Captions and preview
- Local video export
03Space
3D Editor
Compose scenes, import OBJ geometry, edit transforms and materials, then export models, renders, or project files.
- Scene composition
- Materials and transforms
- OBJ and PNG export
04Publishing
World Studio
Build spatial websites, product environments, and immersive case studies from templates, modules, hotspots, IndexedDB drafts, OPFS assets, and a live WebGL preview.
- World templates
- Local-first drafts
- Portable world export
Backstory
The film came first.
HAAM Studio did not begin as a plan to build another creative suite. It began with an unfinished film and years of footage from São Tomé and Príncipe.
I had the material for a movie, but the tools I had were not enough to help me find the movie inside it.
The archive is measured in gigabytes, not clips. There are real interviews, streets, people, accidents, fragments, and images I remember but cannot always find. Some scenes exist. Some are missing. Some transitions were never shot at all.
That changed the brief. The software should ingest large local archives without forcing them into the cloud, make footage searchable, let a film be arranged as scenes and shot placeholders, and make the holes visible. Real camera footage, archive material, and AI generated shots should be able to live in the same filmstrip without pretending they came from the same source.
Instead of designing HAAM Studio in the abstract, the São Tomé film becomes the specification. Every time making the film gets stuck, that friction can become a feature. If I cannot find a conversation, build search. If two scenes do not connect, expose the missing shot. If the shot was never filmed, generate a bridge. If generated material becomes hard to distinguish from documentary material, make provenance part of the interface.
02
Hit a wall
Treat every real production problem as evidence instead of a hypothetical feature request.
03
Build the missing tool
Add only what the film needs: ingest, search, structure, generation, provenance, or export.
04
Use it immediately
The unfinished film is the integration test. The software earns its place by helping the movie exist.
Open the filmstrip editor →
The goal is not to demo the software. The goal is to finish the film with it.
Browser runtime
What this browser can produce locally
Production Studio now reads the same browser capability layer as the labs. The page can show what is ready, what needs a fallback, and where deeper tests live.
Runtime score
0/16
Checking this browser's production runtime…
Storage: unavailable. Persistent storage: unknown.
storage
Local storage
Drafts and larger production assets stay in browser-controlled storage until the user exports or submits them.
- IndexedDBFallback
- OPFSFallback
- Storage estimateFallback
- Persistent storageFallback
media
Media primitives
WebCodecs support prepares the studio for frame extraction, previews, thumbnails, and export preparation.
- VideoFrameFallback
- VideoEncoderFallback
- VideoDecoderFallback
- ImageDecoderFallback
gpu
GPU and rendering
GPU and worker-canvas readiness decides whether heavy previews can move away from the main UI thread.
- WebGPUFallback
- OffscreenCanvasFallback
- Canvas transferFallback
- Dedicated WorkerFallback
compute
Portable compute
WebAssembly support makes local parsers, validators, transforms, compression, and export preparation more plausible.
- WebAssemblyFallback
- ValidateFallback
- CompileFallback
- InstantiateFallback
Local asset vault
A shared source shelf for the whole studio
Add source files once, keep them in this browser’s private OPFS storage, then route them into the photo, video, 3D, or world workspace when the next editing step is ready.
Vault size
0 B
Persistence
Unsupported
Derived outputs
0
Sidecars
0
Browser quota: unavailable. Manifest export includes explicit sidecar metadata and derived lineage without file bytes.
Drop production assets here
Maximum 500.0 MB per file. Assets stay in this browser until explicitly exported.
Checking Production Studio OPFS vault…
image
0
video
0
model
0
world
0
asset
0
- No files saved in the Production Studio asset vault yet.
Production logic
A studio built around outputs
01
Prepare
Shape the source material with focused controls instead of a crowded universal interface.
02
Compose
Make deliberate decisions about framing, sequence, form, and visual hierarchy.
03
Review
Preview the result in the browser before producing a final file or world project.
04
Publish
Create a portable output that can continue into a page, proposal, exhibition, product launch, or another tool.