Why credits instead of seats
Picnie is priced around credits rather than per-seat licenses, because the cost that actually matters is processing - compressing a file, generating an image, running OCR - not how many people happen to be logged in. A five-person team running light, occasional jobs and a one-person account running heavy batch and API traffic have very different real costs, and a credit model reflects that instead of charging both the same seat price.
What the Free plan actually includes
Free accounts come with a starter allotment of credits, enough to try core tools, run a small batch job, and test API calls before committing to a paid tier. The point of the Free plan is evaluation: confirm a tool produces the quality and workflow fit you need, on your own files, before deciding whether the volume justifies upgrading.
How a single action consumes a credit
Most individual actions - a compression, a background removal, a generated image - consume a small, predictable number of credits. Because the cost scales with usage rather than seats, a quiet month costs less and a heavy month costs proportionally more, instead of paying a flat rate regardless of how much processing actually happened.
Batch jobs and how they add up
A batch job is simply many individual actions run together - resizing two hundred product photos consumes roughly the same total credits as resizing them one at a time, just without two hundred separate uploads. What changes with a paid plan is the batch size and frequency limits, since higher tiers are built for teams processing catalogs and campaigns rather than occasional single files.
- Free: smaller batch sizes, enough for testing a workflow
- Paid plans: larger batch sizes and higher monthly credit allotments for regular volume
API usage follows the same logic
Calls through the API reference consume credits the same way manual uploads do - an API-triggered compression or generation costs the same as doing it by hand in the dashboard. This matters when planning an integration: estimate expected call volume against plan limits before wiring automation into a system that could trigger far more requests than a manual workflow ever would.
Choosing a plan based on real usage, not guesses
Instead of picking a tier off the label alone, run a representative week or month of actual work through the Free plan first - a real batch, a real API test - and see how many credits it consumed. That number extrapolates far more reliably to a paid tier than trying to estimate demand in the abstract before using the product at all.
Avoiding surprise overages
The most common surprise is an automation that runs more often than expected - a webhook firing on every minor update instead of only meaningful ones, for example. Check automation triggers periodically, monitor credit usage against the plan on Pricing, and adjust either the trigger conditions or the plan tier before a quiet integration turns into an unexpectedly large bill.
Credits are meant to make cost track usage honestly. Understanding how batch and API actions consume them is what makes that tracking predictable instead of a monthly surprise.
Team accounts and shared credit pools
On team plans, credits typically draw from a shared pool rather than being split evenly per member, which matches how real usage actually looks - one person running a large batch export in a given week and barely touching the tool the next. This avoids the awkwardness of individually rationed allowances while still giving admins visibility into overall consumption, so a team lead can see whether the plan tier still matches how the team is actually working before it becomes a problem.
Deciding when it is time to upgrade
The clearest signal to upgrade is running out of credits before the plan period resets, not just occasionally brushing up against a limit. A single month near the ceiling might just reflect a busy launch; consistently exhausting credits two or three months in a row is a reliable sign that current usage has outgrown the current tier, and upgrading before hitting a hard stop avoids an interrupted workflow in the middle of a batch job or an API-driven pipeline.
Reading the plan comparison before committing
The tiers on Pricing differ not only in credit allotment but often in batch size ceilings and API rate limits, which matter independently of raw credit count for teams running large single jobs versus teams running many small ones spread across a month. Match the plan to the shape of your usage, not just the total volume, and revisit that choice periodically as usage patterns shift.
Picnie at Picnie. Writes about image automation, developer experience, and shipping product faster.