Report bugs through higgsfield.ai/contact: the page lets you pick the channel, quick help in the Higgsfield Discord or direct contact for account-specific issues. Include your browser, OS, a screenshot, and the details of the affected generation: a specific report with reproduction steps is resolved faster than a general description. Submit feature requests in the Discord #suggestions channel, where the product team reads feedback. For platform-wide issues, check the Discord community for incident updates first.
How do I report a bug?
Contact: higgsfield.ai/contact
What to include: your browser name and version, your operating system, a screenshot or screen recording, and a short description of what you expected versus what happened. If the bug involves a specific generation, include its approximate time and the model you used, and the generation's page URL from Assets if it opens.
The more specific the report, the faster it reaches the right team: a report with reproduction steps and the details above is investigated directly.
Found a security vulnerability?
Please report it privately to support@higgsfield.ai so the team can investigate and fix it. We just ask that you keep the details private until it's resolved, as outlined in the Terms of Use: responsible disclosure keeps everyone's accounts safe.
Where do I submit a feature request?
The best place is the Higgsfield Discord server, in the #suggestions channel: discord.gg/higgsfield.
The product, engineering, and CX teams rely on Discord as a real-time signal for what's happening with users. Popular requests and those with strong community signal are prioritized.
What to include: describe what you're trying to do and why the current product doesn't cover it, how often you run into the limitation, and the specific workflow where it shows up. "I want X" is less actionable than "I'm trying to do Y, and the current workflow requires Z extra steps."
What happens after I submit?
Bug reports sent through higgsfield.ai/contact are triaged by the Support team, and bugs affecting users are escalated to engineering. For bugs that resulted in credit loss, include your account email and the details of the affected generation (its approximate time and the model you used) so Support can review and return credits if applicable.
Feature requests via Discord are read by our team. Well-described requests with community signal are added to the product backlog. There is no public roadmap.