Credits measure AI generation usage. Simple generations use fewer credits, while large or premium-model requests use more. BuildUI shows the server-calculated estimate before a paid run.
Help center
Questions about
building with BuildUI.
Clear answers about your code, credits, projects, privacy, and subscription.
Try the free screenshot converter | Explore supported tools | Read implementation guides
Yes. Every account can use Screenshot to Code with GPT-5.6 Luna. No card is required, and you can inspect and export the result before upgrading.
You own the code generated from content you have the right to use. BuildUI does not claim ownership of your uploads or exports.
BuildUI currently supports HTML/CSS, React, Vue, and Next.js generation from prompts, exported images, and PDFs. Flutter, SwiftUI, and Jetpack Compose workflows are labeled coming soon. Direct native Figma-file import is not available—export the target frames first.
Plan credits reset on renewal. Up to one month of unused paid plan credits may roll over while your subscription remains active; reward credits expire after 12 months.
Invite a friend with your unique link. When they verify their email, both of you receive 3 reward credits. If they begin a paid plan, you receive 20 more credits after the refund window. A maximum of 200 reward credits may be earned per month.
Yes. You retain paid access until the end of the current billing period. Credits tied to the subscription expire when access ends; earned reward credits remain available until their stated expiry.
Projects are private to your account by default, authenticated downloads are access-controlled, and project deletion controls are available. Review the Privacy Policy before uploading sensitive material.
Not directly at launch. BuildUI generates an exportable source bundle from prompts, images, and PDFs. Repository-aware changes are planned but remain unavailable until a dedicated, permission-scoped integration is implemented.
We generate semantic structures, keyboard states, labels, contrast-aware defaults, and accessible component patterns. Your team should still validate the final product with real content and users.
Yes. You retain source code you already exported after your plan ends. Projects remain in your account until you delete them, subject to the Terms and any future retention notice.
Credits are automatically restored when BuildUI fails before producing a usable result. You can retry with the same input or choose a different model.
Team collaboration is planned for a future release. The current account model supports secure source ZIP export for handoff through your existing development workflow.
BuildUI sends the inputs you choose to the configured OpenAI API only to perform the requested generation and sets API response storage to false. Review the Privacy Policy and OpenAI's current API data controls before uploading sensitive material.
Still need a hand?
Send the team a note. We typically reply within one business day.