wide-trace/open-higgsfield

A studio for image and video generation — one prompt bar, each model’s own settings, and every finished run in one gallery.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 20th, 2026
Created on August 26th, 2026
Open Issues & Pull Requests: 6 (+0)
GitHub issues: Enabled
Number of forks: 773
Total Stargazers: 3,430 (+4)
Total Subscribers: 25 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 6 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 2
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Detailed Description

Open Higgsfield is a studio for image and video generation that unifies multiple generative models under a single interface.

The tool addresses the fragmentation of working with different image and video generation models by providing a centralized workspace. Rather than switching between separate applications or websites for each model, users enter a prompt once and can generate outputs across multiple models with their individual configuration options. All results accumulate in a shared gallery, making it straightforward to compare outputs and manage generated assets in one place.

The project suits creators and developers who regularly experiment with or deploy multiple generative models. It works well for workflows that involve comparing model outputs, iterating on prompts across different generators, or building applications that need access to several generation capabilities. The unified prompt bar and per-model settings mean you avoid context-switching while retaining the ability to tune each model's parameters independently.

The project shows active development with regular commits across the codebase, indicating ongoing maintenance and feature work. Pull requests are being reviewed and merged, suggesting an engaged development process. The repository maintains a clear separation between client and server components, with TypeScript used throughout, which points to deliberate architectural choices. Documentation and configuration files are present and maintained, reflecting attention to project structure and usability.