2.VIDEO

2.VIDEO is a web workspace that gathers Sora, Veo, MiniMax Hailuo, Seedance and Wan video models behind one form, with text, frame and reference inputs, per-model settings and credit estimates shown before each generation.

2.VIDEO is a web-based AI video generator that puts several third-party video models behind a single form. Instead of signing up with each provider, a user picks a model version from a selector that currently covers OpenAI Sora, Google Veo, MiniMax Hailuo, ByteDance Seedance and Wan, then writes a prompt and submits the task. The site notes that the live selector is the authoritative list, since versions can change with the configured service. The workflow is built around the idea that models differ. Each version exposes only the inputs it actually supports: a text prompt alone, a start frame, an optional end frame, or image, video and audio references. Aspect ratio, resolution and duration options are likewise derived from the chosen version, with clips generally running from 5 to 15 seconds. A credit estimate is calculated from the model and settings and shown before submission, and an option to generate audio sits in the form. Subscriptions and credit packs are handled in a separate pricing flow. Finished clips collect in a Recent Videos history, where they can be previewed, downloaded or regenerated from their saved parameters. A regeneration creates a new task and leaves the earlier result intact, which suits side-by-side comparison of prompts, models and durations. A dedicated Text to Video page strips media fields so a hidden reference cannot slip into a text-only request. The audience is creators, marketers and designers who want to test several leading models without juggling accounts. The page is candid about limits: it makes no claim of a storyboard editor, captions, voiceover or brand presets, and it offers no blanket commercial-rights promise, so usage terms depend on the model provider, source media and plan. Compared with single-model tools, the value here is comparison and cost visibility in one place, while heavier editing would still happen in a separate application.