Overview
What autotube.pro does, how these docs are organized, and where credits fit in.
autotube.pro turns a video title and a channel into a finished YouTube video. You write or import a script, generate a voiceover from it, build the visuals scene by scene, render the video in the cloud, then make a thumbnail and a description. Every step is editable before you move on and can be rerun on its own, and everything the run produces — script, voiceover, images, renders, thumbnail, description and tags — is saved inside one project you can reopen at any time.
How these docs are organized
- Getting started — signing in, your first channel, your first rendered video, using your own script or voiceover, and where everything lives.
- Creating a video — the pipeline steps in order: script, voiceover, visuals, render, description, and the presets and one-shot dialog that run them for you.
- Channels & research — channels hold your defaults; competitors and ideation tell you what to make next.
- Tools — Thumbnails, the Video Editor and the AI Playground.
- Projects — where a video's assets live and how to get back to them.
- Integrations — connecting a YouTube channel and bringing your own API keys.
- Account — plans, billing, credits and account settings.
- Help — what to do when a run fails or something is missing.
Credits, in one paragraph
Work that calls a model — research, script writing, voiceover, images, video clips, descriptions — is paid for in credits, and your balance sits in the top bar next to the coin icon. Before anything paid runs, the app shows an Estimated cost in credits and asks you to confirm, and you are charged for actual usage rather than the estimate. Plans that include a daily render allowance cover rendering separately from credits. See Credits and usage for how a run is priced and where to see what you spent.