Most write-ups about free image generation stop at the credit count. That number tells you almost nothing, because what decides whether a free tier is usable is how much of the pipeline it exposes and where it hard-stops.
I ran a session on PixAI to find out, using one original character as a fixed test subject and staying on features a never-paid account can reach. Three findings are worth passing on, and all three are the kind of thing you only hit by actually running the thing.
The setup
The subject was a surfer with a deliberately over-specified design: turquoise streak on the left of the hair, green eyes, short asymmetric wetsuit with the right arm bare, orange leash on the left ankle, beaded bracelet on the right wrist, shell earring on the right ear, board with three stripes. That gives seven checkable attributes, several of them side-specific and one of them countable.
That is a test harness, not a character sheet. Side-specific and countable attributes fail visibly, which means you can grade an output instead of squinting at it.
Finding one: prompt syntax belongs to the model family, not the platform
The platform hosts two architecture families. The DiT models parse natural-language sentences. The SDXL-derived models respond to tag-style input. Running the same character through one model from each meant rewriting the prompt, not swapping a dropdown.
The rewrite is where things broke. Hair color, the streak, and the eye color carried over. Everything else drifted:
-
orange ankle leash on left anklerendered as orange boots on both feet - the three board stripes vanished entirely
- the shell earring became a turquoise stud
-
right shoulder and arm barecollapsed into a bare shoulder with both sleeves intact
Some of that is the model, and some is my tag translation, and I cannot cleanly separate the two from one test. The transferable point stands either way: switching model families is a prompt rewrite, and every attribute you care about needs re-anchoring in the new syntax. Treat your prompt as source coupled to a target, not as portable input.
Finding two: LoRAs are architecture-bound dependencies
LoRAs are small adapter files that steer a base model toward a specific style, outfit, character, or concept. Free accounts can load them into normal generation, which is the part that makes a free tier interesting rather than decorative.
The dependency behavior is the useful bit. Each LoRA is trained against a specific base model and loads only onto matching ones. The browser has no architecture filter, so the ecosystem solved it socially: creators write the architecture into the LoRA name. Searching dit.2 returns results literally named Yuu_style DiT.2, BotanInk(DiT.2), ColorSnapVibe(DiT.2).
Every LoRA card carries a base model field, and loading the LoRA sets that base model for you. The consequence is worth stating plainly: your adapter choice determines your base model, so on a free account part of your control decision resolves before you generate anything.
One more practical note. The first adapter I picked had a trigger word list running to nine separate instructions, all of them about eyelashes and under-eye detail. The model obliged by building an extra eye onto the character's cheek. Read the trigger list before loading, the same way you would read a package's peer dependencies.
Finding three: a seed does not survive a mode change
The platform offers two generation modes, both open to free accounts, differing in cost and compute. I assumed the cheaper mode would give me the same image at lower fidelity, so I ran one prompt through both with the seed pinned.
It gave me sibling images, not the same image at two quality settings. Measured on a coarse layout comparison, the pair sat inside the same similarity range as two other outputs from the same batch. The prompt explains the resemblance; the seed contributed nothing measurable across the boundary.
That has a workflow implication. If you explore cheaply and find a composition you like, you cannot promote it to the expensive mode by reusing the seed. The modes are separate generations, so explore in whichever mode you intend to finish in.
Where the two modes did differ was background detail. The water carried noticeably less fine texture in the cheaper mode while the face barely changed. One pair is thin evidence for a rule, so run the check on your own subject before committing a day's budget.
What the free tier actually gates
Two categories get conflated constantly, and separating them is most of the analysis:
Unavailable without paying. The fastest generation queue, the video tools, the reference-based consistency tools, and a monthly adapter training allowance. The membership and payment information page carries the specifics, and it is worth reading rather than trusting my summary.
Available, and metered. Everything else. That covers both generation modes, the public model library, community adapters and the standard image sizes. Lean on any of them and the daily allowance drains faster, which is a budget constraint rather than a wall. The free credits guide covers the refill mechanics.
The part I did not expect
I assumed the first generation would be the best one and everything after would be cleanup. The opposite happened. My character's description never fully landed until the fourth stage, after the model and the adapter were settled and the scene had changed completely. The final image carried every specified attribute at once, including the countable one.
For anyone benchmarking a free tier, that is the measurement worth taking. A tier that produces one good image and locks the door behind it is a demo. A tier that lets you converge across four generations is a tool, and the convergence is the thing to test.
The whole session ran to roughly a dozen generation jobs across four configurations, entirely on the free side. If you want to reproduce the method, the platform is here. Pick a subject with side-specific and countable attributes, and grade the outputs instead of admiring them.
Top comments (0)