Short answers grouped by the part of the product they belong to: your account, your credits, and the generation pipeline itself.
Creating an account, verifying your email and understanding the 50 free promotional credits you start with.
Vidrava turns a text prompt into a finished short video. A project moves through script, storyboard, scene media, voiceover, subtitles and render, and every step runs as a background job so you can leave the page and come back to a status update.
Yes. A new account receives 50 promotional credits, recorded as a PROMOTIONAL_CREDIT entry in your credit history. The amount is an admin-configurable pricing rule, so treat 50 as the current default rather than a permanent guarantee.
Verification confirms we can reach you for password resets and payment receipts. Until the link in your verification email is opened, sign-in works but starting a generation job is blocked.
Check your spam folder first, then request a new link from the sign-in screen. Verification links are single-use and expire, so always click the newest one you receive rather than an older message.
The create screen asks for these before anything is generated. Aspect ratio is one of 16:9, 9:16, 1:1 or 4:5, and the choice affects how scene media is framed, so pick the ratio that matches where the video will be published.
How the prepaid credit ledger, reservations and top-ups work, and where to find your payment history.
Credits are prepaid: one US dollar buys ten credits. Each generation step has an estimated credit cost shown before it runs, and every credit movement is written to an append-only ledger so your balance is always the sum of that history, never a number that can be edited directly.
Starting a job reserves the estimated credits immediately, moving them from available to reserved. Reserved credits are excluded from what you can spend until the job either consumes them on success or restores them on failure, which stops two jobs from overspending the same balance.
The checkout form checks the card number and expiry date in your browser before anything is sent. The full card number and the security code are never transmitted to or stored on Vidrava servers; once a payment completes we record only the card brand and the last four digits so you can recognise the payment later.
No. Payment completion is processed through an idempotency key, so replaying the same completion event never adds a second PURCHASE entry to the ledger. If a confirmation is delayed, refreshing Billing will show it once it lands rather than a duplicate.
Dashboard, then Billing, then Payments lists every completed purchase with its amount, credits added and receipt. Credit history is a separate, longer list that also shows promotional grants, reservations and restores.
No. Credits are non-transferable between accounts and have no cash value; they can only be spent on generation inside the account that purchased or earned them.
No. Restoring a reservation returns credits to your available balance inside the ledger when a job fails; it does not touch the original card payment. A refund of an actual charge is a separate process for duplicate charges, unauthorized transactions or billing errors.
Starting a project, understanding the pipeline stages and what happens while a job runs in the background.
A project and a generation job are created, and the job moves through queued, reserving credits, scripting, storyboard, media, voice, subtitles and render stages inside a background worker. You never wait on a request that renders video; you watch the job's status update instead.
The estimated cost is shown so you can decide before any expensive step runs, and starting is blocked if your available balance cannot cover it. This applies to a first generation and to every later regeneration.
A job moves through a fixed sequence of states from draft to queued to the individual pipeline stages, ending in completed, failed or cancelled. Every transition is logged as an event, and the project page polls for the current state so the page reflects real worker progress.
It depends on duration, scene count and current queue load, which is why the project page shows the current pipeline stage rather than a fixed countdown. You can safely close the tab and return later; the job keeps running in the worker.
Yes. The caption track is produced alongside the render as its own asset, so it can be uploaded natively on platforms that prefer separate captions instead of ones burned into the video.
Generated media is private by default and delivered only through short-lived signed URLs tied to your account, not public links. Your prompts and outputs are not exposed to other users or used for public marketing without your consent.
Editing an individual scene, regenerating it and understanding how that affects credit cost and earlier renders.
No. Open the scene editor, change the scene you want to fix and regenerate only that scene. The rest of the video, including its render, is left untouched.
No. Regenerating a single scene is scoped to that scene's media, and its estimated credit cost is shown before you confirm, separately from a full-project regeneration.
Previous renders are kept rather than overwritten, so you can compare an earlier version of the video against the one produced after a scene change before deciding which to keep.
Managing your password, notification preferences, and exporting or deleting your account data.
Use the forgotten-password link on the sign-in page to receive a single-use reset link by email. Opening a new reset link invalidates any earlier one sent for the same account.
Yes. Account settings includes a data export that packages your profile, projects and credit history so you can keep a copy independent of the dashboard.
Deletion removes your personal data and project content. Ledger records required for accurate accounting are retained in an anonymised form, because the credit ledger is append-only and cannot be rewritten after the fact.
What to do when a payment does not appear, a job fails, or a project seems stuck.
Completion is processed as an idempotent background event, so a slow confirmation still appears exactly once when it lands. If it is still missing after several minutes, contact support with the approximate time of the attempt.
When a generation job fails, its reservation is restored to your available balance exactly once, shown as a FAILED_JOB_RESTORE entry in your credit history. You were not charged for the failed attempt, and you can start a new job once the cause is addressed.
The estimated cost of the job is checked against your available balance before it starts. If the estimate is higher than what you have available, the job is blocked so you never end up with a partially reserved balance you cannot cover.
Some pipeline stages, particularly media and render, legitimately take longer than others under load. Each transition is logged, so if a project genuinely stops progressing, contact support with the project reference and we can read its event timeline directly.