Let's look at the plans and storage choices.
This version lists Free, Pro, Pro Plus, and Team.
Free includes five hundred megabytes of managed storage and a ten-megabyte maximum image size.
The current code allows JSON exports on the Free plan.
Pro is listed at nine dollars and ninety-nine cents a month.
It includes fifteen gigabytes of storage and a fifty-megabyte maximum image size.
It also adds the other supported export formats.
Pro Plus is listed at fourteen dollars and ninety-nine cents a month.
It includes one hundred gigabytes of storage and a one-hundred-megabyte maximum image size.
Pro Plus and Team enable the project AI training and AI bounding-box tracking features.
Team is listed at thirty-nine dollars and ninety-nine cents a month.
It includes two hundred and fifty gigabytes of shared storage and three users.
Additional users are listed at four dollars and ninety-nine cents each per month.
For example, one extra user makes the listed base total forty-four dollars and ninety-eight cents before other billing adjustments.
That's thirty-nine dollars and ninety-nine cents, plus four dollars and ninety-nine cents.
Users can manage their subscription, review billing information, update payment details, and cancel through the subscription-management controls.
For Pro Plus and Team, there is also an optional storage feature called bring your own storage.
The user can connect an S3-compatible bucket, including Amazon S3, Cloudflare R2, Backblaze B2, or Wasabi.
They save the connection, test it, and choose whether new uploads should use that bucket.
Managed storage is already included in the plan, so connecting a separate bucket is optional.
When enabled, the new uploads use the user's bucket instead of the included managed storage.
The storage provider's own costs and connection settings still belong to that separate storage setup.
Now let's move to AI Studio.
The general workflow is to describe the result, choose the settings, check the credit price, and create the job.
The recent-creations section shows progress and provides the output when it's ready.
The Image Generator creates images from a written description.
For example, I could describe a parking lot, the camera viewpoint, the lighting, the weather, and the objects that should be visible.
I can choose the number of outputs, quality, and square, landscape, or portrait shape.
The supported request range is one to ten images.
The listed quality choices cost two credits per draft image, eight per standard image, and twenty-nine per premium image.
So four standard images cost thirty-two credits.
That's four times eight.
The price updates before creation.
The Image Editor starts with uploaded images.
I can provide one to ten reference images and describe the change I want.
Then I choose the number and settings of the output images.
This is an AI-directed edit, so I inspect the result to check whether the parts I care about were preserved.
If I need to resize, crop, or convert a file using exact settings, I can use the Image Toolkit in Media Tools.
The visual-generation code sends requests through a configured Runway API connection.
The website handles the account, settings, job progress, charging, and private output delivery around that generation service.
The Video Generator starts with a text description and can also use a reference image.
I choose the duration and resolution, then check the displayed price.
The duration choices are five, ten, fifteen, thirty, and sixty seconds.
Longer outputs are made from shorter generated scenes and combined into one MP4 file.
The scene prompts ask for the same subjects, setting, and visual style throughout.
I would still inspect the scene joins and subject consistency.
Asking a model to preserve a character doesn't guarantee that every scene will match perfectly.
The listed resolutions are four eighty P, seven twenty P, and ten eighty P.
When a reference image is used, the current video-generation workflow supports up to seven twenty P.
To use ten eighty P, the request needs to be text-only.
The price depends on duration and resolution.
In this version, seven twenty P costs eighteen credits per second.
A five-second request at that resolution costs ninety credits.
That's five times eighteen.
The interface calculates the selected request before submission.
Generation can take time, so for a walkthrough I can explain the settings and show an existing result instead of waiting for a new video to finish.
AI Studio also has a tool called Create Your Dataset.
This creates a collection of generated images or frames.
The maximum requested size is three thousand files.
There are two modes: independent images and sequential frames.
Independent images are generated as separate image outputs from the written prompt.
I choose the count, image quality, and shape.
In this implementation, the independent-image workflow uses the prompt. It doesn't apply the optional reference image as guidance.
Sequential frames work differently.
The tool generates video clips and extracts frames at the selected rate.
The choices are six, twelve, or twenty-four frames per second.
I can also choose the resolution.
The sequential workflow can use a reference image, with the same seven twenty P restriction for image guidance.
Sequential output contains neighboring frames within the generated clips.
If a large request needs more than one clip, I would inspect the boundaries between clips.
The files aren't proof of one physically consistent continuous recording.
The results come in ZIP parts with up to one hundred files per part.
Each part includes a manifest.
The manifest records information such as the prompt, dataset mode, and file range.
That makes a large result easier to download and identify.
The output is synthetic imagery.
It doesn't include automatically reviewed object labels.
If I need a labeled detection dataset, I still need to annotate the images, check the labels, and evaluate whether the generated examples are useful for the real task.
I would also keep synthetic examples identifiable when studying how they affect model performance.