Usage and limits

Building and iterating spend credits from your workspace's balance. Knowing how it's counted helps you plan.

What counts

Each build and edit spends credits, charged on the real model spend for that run and rounded up to a whole credit — with a minimum of one per charged run.

What doesn't cost anything:

• Opening and clicking through the preview
• Reading your code, browsing tables, or looking at logs
• Undo and rollback, which don't call a model at all

For exactly how credits are metered and how to get more, see Plans and credit usage.

Shared across a team

Everyone in a workspace draws from the same pool, so usage reflects your whole team's activity, not one person's.

At the limit

When your balance reaches zero, new builds and edits are blocked until credits are available again — you'll get a clear message rather than a failed build. Upgrade, add credits, or wait for the next grant.

Published apps keep running either way. Limits apply to building, not to your live app's traffic.

On the Free plan, credits arrive daily rather than as one monthly lump: 5 build credits a day, up to 30 in a calendar month. Daily credits don't roll over — whatever you don't use is gone at the end of the day, and a fresh 5 arrive the next.

Attaching files

You can attach files to any chat message to give Vorx context — a screenshot or design reference, a PDF or document to build from, a spreadsheet or CSV to model data on, or any other file. Any file type is accepted: Vorx reads images, documents, and data directly, and keeps other files available for your app to use or link to.

You can attach up to 10 files per message, and each file can be up to:

• 20 MB per file on the Free plan
• 256 MB per file on paid plans

These are limits on what you attach to chat. Files your app's users upload are a different thing — see Files and storage.

Use it efficiently

• Make focused, specific edits — but don't split a change so finely that you pay the one-credit floor five times over for what one prompt could do.
• Use Plan mode to get an approach right before building it.
• Review each change before sending the next, so you're not paying to build on top of something wrong.
• Watch the credits line under each reply — it's the fastest way to learn what an expensive turn looks like.

Next steps

• Plans and credit usage — the full picture
• Plans and billing — invoices and payment
• Teams — shared usage