FAQ
Straight answers about first image timing, ComfyUI continuity, local privacy, account requirements, and the difference between Sweet Tea and the machinery underneath it.
Sweet Tea Studio is for making AI images and video without letting setup take over the whole session. Start with one tool, make something good, save what worked, and come back to it later. If you already use ComfyUI, you can keep it. If you do not, you can still start here.
Make portraits, product images, concept stills, story frames, variations, short clips, and cleanup passes. The point is to make something you would want to keep, not spend the whole time managing the setup.
No. Sweet Tea is meant to let you start with a tool that already fits the job and change the settings that matter. Knowing more about ComfyUI can help later, but it is not required for a first image.
Yes. If you already have a setup you like, Sweet Tea can work with it instead of making you start over.
No. Generation happens on the engine you run, usually on your own machine and sometimes on hardware you control elsewhere.
No. The website is for downloads, docs, your account, and the things you save there. The Studio app is where you actually make images and video.
Yes. Local generation stays local. Data leaves your machine only when you deliberately use a cloud, sync, or publishing feature.
No.
Sweet Tea shows you what is missing and points you at the specific problem, so you are not left guessing which model or add-on broke the run.
You can. Sweet Tea is for the part after that decision: pick a tool, change the settings that matter, keep the project together, and get back to a version you liked without digging through everything again.
A working generation engine, at least one compatible model file, and enough disk space for the app, the model, and your outputs. If you already use ComfyUI, Sweet Tea can point to that setup.
Windows and Linux.
No. Internet is only needed for downloading models or nodes, browsing web features, or using a remote setup.
No. You can generate without a GPU.
Because GPU generation is much faster. CPU generation works, but it is usually slow enough that most people treat it as a fallback or testing path.
Yes. Sweet Tea can connect to a remote engine, but that is usually a later step. If you can, get one clean local run working first.
Sweet Tea does not force engine updates. Most breakage comes from changing ComfyUI, custom nodes, or model files. Sweet Tea’s job is to make those problems visible and easier to fix.
No. ComfyUI is still the engine. Sweet Tea is the workspace around it: tools, projects, prompts, outputs, and saved settings in one place.
No. Automatic1111 is more screen-and-tab driven. Sweet Tea is built around reusable tools, saved project context, and getting back to a result you liked.
The Pipe file itself (.tea or workflow .json) is a description of how the job runs. The bigger trust question is what it asks you to install around it, especially custom nodes. Treat new dependencies the same way you would treat installing software from the internet.
No. Your engine is still yours, your model files are still yours, and your work does not become trapped in Sweet Tea. The point is to make the day-to-day part easier, not to box you in.
Sweet Tea Community can be used for free on your own machine. Sweet Tea Plus is there if you want easier setup, tested tools, and your saved work available across devices.
No.
Only what you choose to publish, usually the Pipe plus a preview and listing metadata. Publishing is opt-in.
Yes.
No. Sweet Tea Studio is its own app. ComfyUI, custom nodes, and models keep their original licenses, and using Studio does not change those obligations.