What are the backend limits in Wix Studio Two?

Every Studio Two site gets the same fixed backend, whatever its plan: one backend instance per data centre, 300 millicores of CPU, 400 MB of memory, a 60 second timeout per request, and instances that are recycled every 5 minutes. There's no auto-scaling of backend code. For most business sites that's plenty. For heavy processing, it isn't.

What do the limits mean in practice?

• CPU, 300 millicores. That's about a third of a core. Go over and your code is throttled, so it slows down rather than failing.
• Memory, 400 MB per instance. Big files or large data sets held in memory can hit this.
• Timeout, 60 seconds. A request that runs longer returns a 504 error.
• Uptime, 5 minutes. Instances are recycled, so never keep state in global variables. Store it in the CMS or another service.
• One instance per data centre. Requests in that region share it.

That's a change from the Wix Editor and Wix Studio, where Wix says backend limits depend on the premium plan.

How do you work within them?

1. Keep backend functions short and stateless.
2. Split bulk jobs into batches that each finish well inside 60 seconds.
3. Watch the logs for slow code. Studio Two keeps logs for 24 hours, and only captures entries written with Wix's monitoring client, not console output. You can forward logs to OpenTelemetry to keep them longer.
4. Remember there are no scheduled jobs in this release, so plan nightly tasks another way.

If a project needs heavy server work, Studio Two may not be the right home for that part. A headless build with its own backend is one alternative. See our Wix Headless service, or our Wix development team for code-heavy builds. If you're weighing up a Studio Two build, start with our Wix Studio 2 service.