WebToAppConvert uses a credit-based model rather than a monthly subscription for most users. You buy credits, spend them on builds, and the credits don't expire. This means you pay for what you use, not for months when you're not building anything.
Free Account
When you sign up, your account receives 20 free credits. This is enough to run two Debug builds (10 credits each). Debug builds produce unsigned APKs for testing on your own device: they cannot be submitted to Google Play.
Free accounts can create up to 3 apps. Build artifacts (APKs and AABs) are retained for 7 days before being automatically deleted.
Paid Account (Credit Packs)
Purchasing any credit pack upgrades your account. Credits never expire. You can buy more credits at any time and they stack with your existing balance.
Credit pack pricing:
- 150 credits: $15
- 350 credits: $30
- 1000 credits: $80
Build credit costs:
- Debug: 10 credits: unsigned APK, testing only
- Starter: 50 credits: signed AAB, custom branding, splash screen, intro screens
- Professional: 100 credits: everything in Starter plus Firebase push notifications, Google AdMob, file upload/download support
On a paid account, build artifacts are retained for 30 days. You can create up to 10 apps. Subscribing to a monthly plan removes this cap entirely.
Subscription Account
Subscribed accounts receive unlimited builds for a fixed monthly fee. Build artifacts are retained indefinitely (as long as the subscription is active). Subscriptions are best suited for agencies or teams that build apps regularly for multiple clients.
See the Pricing page for current subscription tier pricing.
Choosing the Right Approach
| Scenario | Recommended Option |
|---|---|
| Testing before committing | Free account + Debug builds |
| Single app, build once or twice per year | 150-credit pack ($15) |
| Single app with ongoing updates | 350-credit pack ($30) |
| Agency building for multiple clients | 1000-credit pack ($80) or subscription |
| High-volume recurring builds | Subscription |
Feature Availability by Plan
| Feature | Free | Paid (Starter Build) | Paid (Professional Build) |
|---|---|---|---|
| Debug APK | ✓ | ✓ | ✓ |
| Signed AAB (Google Play ready) | — | ✓ | ✓ |
| Custom app icon | ✓ (debug only) | ✓ | ✓ |
| Splash screen | — | ✓ | ✓ |
| Intro / onboarding screens | — | ✓ | ✓ |
| Custom signing key | — | ✓ | ✓ |
| Firebase push notifications | — | — | ✓ |
| Google AdMob integration | — | — | ✓ |
| File upload support | — | — | ✓ |
| File download support | — | — | ✓ |
| Build artifact retention | 7 days | 30 days | 30 days |
| Max apps | 3 | 10 | 10 |
Can I Upgrade a Debug Build to a Production Build?
No: Debug and production builds are separate build jobs. Once you're satisfied with how your debug build performs, you initiate a new Starter or Professional build using the same app configuration. The signed AAB uses your selected signing key, not the debug key.