invideo AI's text-to-video route, read for what goes in

The page read here is invideo's pricing page. It states agents and generative models beside a timeline, stock and your own footage, voice tools, and credits that do not roll over. No route for bringing an existing script or novel in as source is stated. The register's rows below show what a documented intake answers. From 7 source pages, read 2026-09-25; no maker pays to be listed.

1What this register already recorded

The register's rows for four printed file routes and four stated ceilings — the shape an intake takes when a vendor writes it down.

• Formats
  PDF, FDX, Fountain, Word or TXT scripts, or a shot list imported from ExcelFAQ: how does it workStoryboarder.ai, home page FAQ / recorded 2026-09-25
• Formats
  A .txt or .docx file is uploaded, or text pasted directlyupload scriptPippit, one sentence one drama guide / recorded 2026-09-25
• Formats
  Plain text (.txt) files only, per the FAQFAQ: supported formatsLTX Studio, script to video page / recorded 2026-09-25
• Formats
  Any text: rough outlines, bulleted lists or formal screenplaysFAQ: what script formatsPexo, script to video page / recorded 2026-09-25
• Length
  Scripts of up to 100 pagesupload your scriptDrawstory, home page / recorded 2026-09-25
• Length
  Scripts up to 12,000 characterslonger dramatic videosMagicLight, AI Drama Generator page / recorded 2026-09-25
• Length
  Scripts of up to 100,000 words, per the FAQFAQ: maximum script lengthPixmax, AI Video Agent page / recorded 2026-09-25
• Languages
  A script in any language is accepted; results are translated to EnglishFAQLTX Studio, script to video page / recorded 2026-09-25

2What invideo's own page states

invideo's page describes a studio: AI agents and generative models working beside an editing timeline, with stock footage and your own footage as the material, 4K export, and a voice generator that can clone a voice. Editing is listed as a full timeline with colour, audio and 3D tools and multiplayer seats.

On intake it states footage and credits. No line read names a paste box, an upload or an import for an existing script, story or novel. That is a statement about the page read, not about the product, and the rows below are what the same register holds where a vendor does print the route.

3What a documented intake answers

File types, when printed, are a short list. storyboarder takes PDF, FDX, Fountain, Word or TXT, plus a shot list imported from Excel. Pippit takes .txt or .docx, or text pasted directly. LTX Studio takes plain .txt only, per its FAQ. Pexo takes any text: rough outlines, bulleted lists or formal screenplays.

Ceilings come in four units in this register and three appear here: pages (up to 100), characters (12,000) and words (100,000). One language line sits beside them: a script in any language is accepted with the results translated to English. A text-to-video search rarely asks any of this; a manuscript does.

4Why the route has to be printed

The register admits a tool when its own page names a route for bringing an existing script, story, novel or chapter in as the source, and answers two of the six checkpoints. A prompt box is not a route for a novel. A line of text is a line; a manuscript needs an address it can be delivered to.

So the two halves of a text-to-video search part here: the studio half is answered by the vendor's own page above, and the intake half is answered a row at a time below, by vendors who wrote down what they accept. The register does not guess at the first from the second.

5What the counts around the model say

The gathered material counts the model family below in five figures and puts it at a large share of one subreddit's posts; the counts table and the share table both come from the collection, not from the register. Talk about a model says nothing about what a tool accepts as source text.

That is why the two sit on one page without being mixed. The counts are printed as counts, the register's rows are quoted with their dates, and the question this page started from — what goes in — is answered only by the pages that state it.

6What each tool states on its own pages

Inclusion rule. Named here: the tools this page reads, and the pipeline whose intake rows this register already keeps. A cell carries the page's own wording; the pipeline's cell is one sentence quoted from its published guides. A checkpoint the pages do not answer is left as an open cell rather than filled from a demonstration. Order. Alphabetical by tool name.

7What the collected threads asked

The names counted below are the model family the material discusses most in this corner, printed as counts rather than as intake facts.

Inclusion rule. Names carried in the gathered material and read on this page. A thread arguing with itself can be counted in the positive column and the negative column both. Order. Descending by posts.

Inclusion rule. Model families the collection put a share against, out of the posts it read in that subreddit. Order. Descending by the share as printed.

8When the tool's own route is the simpler one

• The studio is the product — Agents, a timeline and your own footage in one place suit work that is assembled rather than adapted from a manuscript.
• Editing arrives with the model — A full editing timeline with colour, audio and 3D tools means the cut is part of the same seat as the generation.
• Voice tools are on the page — An AI voice generator and voice cloning are stated features, which is what a narrated piece needs from its tool.

The search behind this page asks for invideo as a text-to-video tool; its own page describes agents and footage, and the intake register keeps a separate row for every route like it. Two more reads sit beside this one: OpenArt's story route and Vidu's references.