Field, a local-first studio for AI media and launch videos

TL;DR

• Field is a local creative studio for AI media generation: images and videos from the available Higgsfield models, a visual workspace and a timeline editor that exports an MP4.
• Launchframe turns a public product URL into a plan, then a brief with video types, budget and an approval workflow, then an assembled video — all assembled on your machine with ffmpeg.
• Projects and Launchframe media stay on your computer; the README is explicit that it is a personal local app, not a shared hosting service.
• Without provider keys it uses clearly marked demo or catalog results instead of pretending a live render happened.

What it is and who it is for

Field — Recreate Higgsfield is a local-first creative studio for AI media generation, visual workflows, editing and product-launch videos. It is displayed as four screens: home with image, video, audio, 3D and Launchframe modes; a create screen with a sample prompt and generation settings; a visual workspace with generator, launch and editor nodes; and a timeline editor with preview, media library and export controls.

It is for the person who already generates media and loses the results across five browser tabs, and for the one who needs a launch video for a product and does not want to storyboard it by hand.

What you can do

• Generate images and videos with the available Higgsfield models.
• Connect compatible generators and tools in the visual Workspace, then send media to the Editor.
• Arrange image, video and audio clips on a timeline and export an MP4.
• Turn a public product URL into a Launchframe plan, review it, approve production, and assemble the result locally.
• Search Pexels for stock footage when a Pexels API key is configured.

Audio and 3D generation screens are included, but the README is honest about what that means: live API availability depends on the Higgsfield endpoints and permissions available to your account. The app reports provider errors when an endpoint is unavailable, and without credentials generation uses clearly marked demo or catalog results instead of claiming a live render. That distinction is the difference between a demo that lies and a demo that says it is a demo.

Requirements and quick start

Node.js 22.9 or newer, npm, and ffmpeg on PATH for Launchframe video assembly — brew install ffmpeg on macOS, an ffmpeg package on Linux or Windows.

git clone https://github.com/artificialguybr/recreate-higgsfield.git
cd recreate-higgsfield
npm ci
cp .env.example .env
npm run build
npm start

Open http://127.0.0.1:3000. The .env copy is optional, and demo or catalog mode stays available without provider keys. For frontend development, keep the backend running with npm start and run npm run dev in another terminal, then open the Vite URL it prints (default http://localhost:5174); if you change PORT, use the same value in both processes.

Keys, data and the network boundary

Provider credentials go in the local .env file. The README's two rules are that no secret is ever prefixed with VITE_ and .env is never committed.

The server binds to loopback by default because its local API proxies use your provider keys, so the README warns against HOST=0.0.0.0 or exposing the port to a network. That is a sensible default in an app whose whole selling point is that the keys and the media stay local.

Launchframe data lives outside the repository, under ~/.recreate-higgsfield/launchframe-data or the equivalent home directory on your OS, and FIELD_DATA_DIR moves it. An empty new data directory is populated from the legacy repository-level launchframe-data/ on first run, and the old copy is not deleted automatically.

Two things to know before you rely on it

The first is ffmpeg. Launchframe assembly requires the system executable, while the Editor's browser-based export loads an ffmpeg WebAssembly core from jsDelivr the first time it is used — so that export needs an internet connection even though the rest is local.

The second is the license. The README states that no license file is included yet and that you should ask the repository owner before reusing or redistributing the project, which is worth checking before shipping it as part of anything.

When to use it, when not to

Use it when you already generate media and want a workspace and a timeline in one place instead of five tabs, when a launch video has to be produced from a product URL without a storyboard session, or when you want the media pipeline to stay on your machine.

Do not use it as a hosted service or a team tool, and do not use it expecting every model to be live: availability depends on the endpoints and permissions of your account. And do not expose the port — the local API proxies your keys.

Sources

1. Field — Recreate Higgsfield — repository — screens, capabilities, requirements, quick start, environment table, data and export notes and license status quoted above.
2. README.md — quick start, environment variables, data directory, license.

Project page: Field — Recreate Higgsfield

For assembling a longer video pipeline locally, see the ComfyUI film production pipeline, and for the directing layer above it, HyperFrames Video Director.

FAQ

Does it need API keys? Only for live generation. Higgsfield keys enable live generation; without them the app runs in clearly marked demo or catalog mode, and a Pexels key is optional for stock footage.

Does it run offline? The app runs locally, but the Editor's browser export loads the ffmpeg WebAssembly core from jsDelivr the first time, so that export needs a connection.

Where are projects stored? Outside the repository, under ~/.recreate-higgsfield/launchframe-data or the equivalent home folder, and FIELD_DATA_DIR moves it.

Can I expose it to my network? The README advises against it: the server binds to loopback because its local API proxies use your provider keys.