Runway Web Credits vs API Pricing: What Each Balance Covers

Short answer

Runway has two credit systems that should be budgeted separately. Web app credits live with Runway plans and purchased web credits in the creator workspace. API credits live in the Runway developer portal for an API organization. Runway's Help Center says web app credits and API credits are completely separate, so a creator subscription does not become an API budget and API credit purchases do not refill the web app.

That boundary matters because the two surfaces publish different buying logic. The web pricing page sells per-editor app plans with included credits, workspace limits, export features, storage, and Enterprise options. The API pricing docs sell developer credits at $0.01 per credit and then charge different model rates by second, image, audio length, upscale, or real-time session.

Use the web app when a human is prompting, editing, exploring shots, working in Runway sessions, managing creative assets, and exporting finished work. Use the API when software needs to generate or edit media from a product, backend job, CMS, internal tool, or customer-facing workflow.

Web subscription credits

Monthly web plan credits are not a stored savings account. Runway says Standard, Pro, and Unlimited credits refresh monthly, do not roll over, and reset around the billing date. Purchased web credits are different: Standard, Pro, and Unlimited users can buy more from Plans & Billing, the minimum purchase is 1,000 credits, and purchased credits do not expire. Enterprise documentation adds that up to $9,999 worth of credits can be purchased in-app, with larger quantities routed through the account team or sales.

Workspaces also change the credit math. Runway says pricing is per editor and that added editors are charged according to the admin's billing choice, but one set of plan credits is shared per workspace. Adding a second Standard editor to the same workspace does not create a second 625-credit monthly allowance. If the business goal is multiple independent credit pools, the official guidance points toward separate disconnected subscriptions rather than collaborators in one workspace.

API credits and model costs

Runway API usage starts from a developer organization, not a web app plan. API credits are purchased in the developer portal at $0.01 per credit, and each API generation consumes credits according to the selected model and output. Autobilling can top up an organization when its balance falls below a threshold; the automatic recharge amount must be at least 1,000 credits, or $10, and the actual ability to spend is constrained by the organization's usage tier.

The API cost table is model-specific. For video generation, Runway lists gen4.5 at 12 credits per second, gen4_turbo at 5 credits per second, gen4_aleph at 15 credits per second, gen3a_turbo at 5 credits per second, act_two at 5 credits per second, veo3 at 40 credits per second, veo3.1 with audio at 40 credits per second, veo3.1 without audio at 20 credits per second, veo3.1_fast with audio at 15 credits per second, and veo3.1_fast without audio at 10 credits per second.

Images and related media use their own API meters. Runway lists gen4_image at 5 credits per 720p image or 8 credits per 1080p image, gen4_image_turbo at 2 credits per image, gemini_image3_pro at 20 credits per 1K or 2K image and 40 credits per 4K image, and gpt_image_2 as a quality-and-resolution range from 1 to 41 credits per image. The same pricing docs also publish separate rates for upscaling, text-to-speech, sound, voice isolation, dubbing, speech-to-speech, and real-time avatars.

This is why web credit examples should not be reused as API estimates. A web plan card can translate a monthly web allowance into seconds of selected Runway models, while the API page publishes a separate developer pricing table. Keep the source surface matched to the spend surface: web plan credits for app usage, API credits for API tasks.

Team and organization boundaries

For creative teams, the relevant boundary is the Runway workspace. Standard supports up to 5 users per workspace, Pro and Unlimited support up to 10, and Enterprise is positioned for larger organizations with configurable organization and team spaces. Because workspace credits are shared, a team should estimate combined editor activity, not just each editor's personal workload.

For developer teams, the relevant boundary is the API organization. Runway's API docs let organizations add members so teams can share key management, usage stats, and billing setup. The permission model is broad: members can take the same actions as the organization owner except removing that owner. Removing a person from the organization does not revoke org-scoped API keys, so production API teams need key rotation and disabled-key procedures as part of their cost and access controls.

Usage tiers matter for API production planning. Runway sets API limits per organization and per model, including concurrency, daily generations, and maximum monthly spend. Higher tiers unlock larger limits after more credit spend. If an app needs predictable volume, the budget question is not just cost per second; it is also whether the organization can buy enough credits, run enough concurrent tasks, and stay within the daily generation limits.

Choosing the right route

Choose the web app when the work is creative and human-paced: storyboarding, prompting, iterating shots, editing outputs, managing assets, using Runway's apps, and exporting finished media. Standard is the entry paid route when Free is too small, Pro fits heavier recurring credit usage, Unlimited fits creators who can benefit from Explore Mode, and Enterprise fits organizations that need custom credits, security, support, and workspace governance.

Choose the API when the output has to be generated by software. Good API triggers include a product feature that creates videos for users, a CMS workflow that generates media from records, a batch pipeline, an internal creative operations tool, or any workflow that needs API keys, usage logs, spend limits, retries, and integration testing. In that case, plan around the API model rates, the 1-cent credit value, autobilling settings, and usage-tier ceilings.

Do not mix the budgets during approval. A Runway web subscription may still be useful for creative direction, manual review, and prompt testing, while API credits pay for the automated system. Treat those as two line items unless Runway changes the official boundary between web and API balances.

The safest final check is to model one real workflow on the correct surface. For web, count editors, expected monthly generations, rejected attempts, export needs, and whether credits reset before the next project. For API, count task volume, seconds or images per task, model choice, retries, concurrency, monthly spend caps, and the minimum credit top-up needed to avoid failed production runs.