Skip to content
Notifications
Clear all

Anyone else having billing issues with the 'credits' system? It's opaque.

2 Posts
2 Users
0 Reactions
0 Views
(@fionac)
Estimable Member
Joined: 1 week ago
Posts: 61
Topic starter   [#14031]

Hi everyone. I'm fairly new to Resemble AI, using it for some basic voiceover work in our email campaign videos. I'm still learning the ropes of the platform itself.

I've run into something confusing with the billing and credit system. Last month, I generated a few short clips, and my credit usage seemed to line up with what I expected. This month, however, the dashboard showed a significant chunk of credits were used almost immediately. I can't find a detailed breakdown of what consumed them—was it the number of characters, the voice model used, or maybe the download format? The invoice just shows "credits used" with a total.

Has anyone else found it difficult to predict their monthly credit burn? I want to budget this tool into our campaign management, but the opacity makes it hard. For example, does cloning a new voice use a different amount of credits than generating speech from an existing model? I couldn't find clear tiers or a calculator.

I’m trying to be methodical about learning this tool, but this part feels like a black box. Any insights on how you track or estimate your usage would be really helpful.



   
Quote
(@ethanv)
Estimable Member
Joined: 1 week ago
Posts: 117
 

Yeah, the credit breakdown is definitely a pain point. I ran into a similar surprise last quarter - a project used a 'premium' voice model and the credit cost was almost double per character compared to the standard ones, but that multiplier wasn't obvious until I saw the total.

A few things that helped me track it better:
- The cost can depend on voice tier, output format (HD audio uses more), and whether you're using neural speech vs. cloning. Cloning a new voice is a big, one-time credit sink.
- I started exporting my project history manually and matching timestamps to my invoice. It's extra work, but it gave me a rough map.

I'd love a proper usage log or a billing API. For now, treating it like a metered utility with a buffer is the safest bet.


Ship fast, measure faster.


   
ReplyQuote