Stay organized with collections
Save and categorize content based on your preferences.
This page describes how to prepare video training data for use in a
Vertex AI dataset to train a video classification model.
The following sections provide information about data requirements,
schema files, and the format of the data import files (JSONL & CSV) that are
defined by the schema.
Alternatively, you can import videos that have not been annotated and
annotate them later using the Google Cloud console
(see Labeling using the Google Cloud console).
Data requirements
The following requirements apply to datasets used to train AutoML
or custom-trained models.
Vertex AI supports the following video formats for training
your model or requesting a prediction (annotating a video).
.MOV
.MPEG4
.MP4
.AVI
To view the video content in the web console or to annotate a video, the video
must be in a format that your browser natively supports.
Since not all browsers handle .MOV or .AVI content natively, the
recommendation is to use either .MPEG4 or .MP4 video format.
Maximum file size is 50 GB (up to 3 hours in duration). Individual video
files with malformed or empty timestamps in the container aren't supported.
The maximum number of labels in each dataset is limited to 1,000.
You may assign "ML_USE" labels to the videos in the import files. At
training time, you may choose to use those labels to split the videos and
their corresponding annotations into "training" or "test" sets. For video
classification, note the following:
At least two different classes are required for model training. For
example, "news" and "MTV", or "game" and "others".
Consider including a "None_of_the_above" class and video segments that
do not match any of your defined classes.
Best practices for video data used to train AutoML models
The following practices apply to datasets used to train AutoML
models.
The training data should be as close as possible to the data on which
predictions are to be made. For example, if your use case involves blurry and
low-resolution videos (such as from a security camera), your training data
should be composed of blurry, low-resolution videos. In general, you should
also consider providing multiple angles, resolutions, and backgrounds for
your training videos.
Vertex AI models can't generally predict labels that humans
can't assign. If a human can't be trained to assign labels by looking at the
video for 1-2 seconds, the model likely can't be trained to do it either.
The model works best when there are at most 100 times more videos for the
most common label than for the least common label. We recommend removing low
frequency labels. For video classification, the recommended number of training
videos per label is about 1,000. The minimum per label is 10, or 50 for advanced
models. In general, it takes more examples per label to train models with
multiple labels per video, and resulting scores are harder to interpret.
Schema files
Use the following publicly accessible schema file when creating the
jsonl file for importing annotations. This schema file dictates the format of
the data input files. The structure of the file follows the
OpenAPI Schema
test.
title: VideoClassification
description: >
Import and export format for importing/exporting videos together with
classification annotations with time segment. Can be used in
Dataset.import_schema_uri field.
type: object
required:
- videoGcsUri
properties:
videoGcsUri:
type: string
description: >
A Cloud Storage URI pointing to a video. Up to 50 GB in size and
up to 3 hours in duration. Supported file mime types: `video/mp4`,
`video/avi`, `video/quicktime`.
timeSegmentAnnotations:
type: array
description: >
Multiple classification annotations. Each on a time segment of the video.
items:
type: object
description: Annotation with a time segment on media (e.g., video).
properties:
displayName:
type: string
description: >
It will be imported as/exported from AnnotationSpec's display name.
startTime:
type: string
description: >
The start of the time segment. Expressed as a number of seconds as
measured from the start of the video, with "s" appended at the end.
Fractions are allowed, up to a microsecond precision.
default: 0s
endTime:
type: string
description: >
The end of the time segment. Expressed as a number of seconds as
measured from the start of the video, with "s" appended at the end.
Fractions are allowed, up to a microsecond precision, and "Infinity"
is allowed, which corresponds to the end of the video.
default: Infinity
annotationResourceLabels:
description: Resource labels on the Annotation.
type: object
additionalProperties:
type: string
dataItemResourceLabels:
description: Resource labels on the DataItem.
type: object
additionalProperties:
type: string
Input files
The format of your training data for video classification are as follows.
To import your data, create either a JSONL or CSV file.
ML_USE (Optional). For data split purposes when training
a model. Use TRAINING or TEST.
VIDEO_URI. This field contains the Cloud Storage URI
for the video. Cloud Storage URIs are case-sensitive.
LABEL. Labels must start with a letter and only contain
letters, numbers, and underscores. You can specify multiple labels for
a video by adding multiple rows in the CSV file that each identify the
same video segment, with a different label for each row.
START,END. These two columns, START and END,
respectively, identify the start and end time of the video segment to
analyze, in seconds. The start time must be less than the end time. Both
values must be non-negative and within the time range of the video. For
example, 0.09845,1.36005. To use the entire content of
the video, specify a start time of 0 and an end time of
the full-length of the video or "inf". For example, 0,inf.
You can also provide videos in the data file without specifying
any labels. You must then use the Google Cloud console to apply labels to
your data before you train your model. To do so, you only need to
provide the Cloud Storage URI for the video followed by three commas,
as shown in the following example.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Prepare video training data for classification\n\nThis page describes how to prepare video training data for use in a Vertex AI dataset to train a video classification model.\n\n\u003cbr /\u003e\n\nThe following sections provide information about data requirements,\nschema files, and the format of the data import files (JSONL \\& CSV) that are\ndefined by the schema.\n\nAlternatively, you can import videos that have not been annotated and\nannotate them later using the Google Cloud console\n(see [Labeling using the Google Cloud console](/vertex-ai/docs/datasets/label-using-console)).\n\nData requirements\n-----------------\n\nThe following requirements apply to datasets used to train AutoML\nor custom-trained models.\n\n- Vertex AI supports the following video formats for training\n your model or requesting a prediction (annotating a video).\n\n - .MOV\n - .MPEG4\n - .MP4\n - .AVI\n- To view the video content in the web console or to annotate a video, the video\n must be in a format that your browser natively supports.\n Since not all browsers handle .MOV or .AVI content natively, the\n recommendation is to use either .MPEG4 or .MP4 video format.\n\n- Maximum file size is 50 GB (up to 3 hours in duration). Individual video\n files with malformed or empty timestamps in the container aren't supported.\n\n- The maximum number of labels in each dataset is limited to 1,000.\n\n- You may assign \"ML_USE\" labels to the videos in the import files. At\n training time, you may choose to use those labels to split the videos and\n their corresponding annotations into \"training\" or \"test\" sets. For video\n classification, note the following:\n\n - At least two different classes are required for model training. For example, \"news\" and \"MTV\", or \"game\" and \"others\".\n - Consider including a \"None_of_the_above\" class and video segments that do not match any of your defined classes.\n\nBest practices for video data used to train AutoML models\n---------------------------------------------------------\n\nThe following practices apply to datasets used to train AutoML\nmodels.\n\n- The training data should be as close as possible to the data on which\n predictions are to be made. For example, if your use case involves blurry and\n low-resolution videos (such as from a security camera), your training data\n should be composed of blurry, low-resolution videos. In general, you should\n also consider providing multiple angles, resolutions, and backgrounds for\n your training videos.\n\n- Vertex AI models can't generally predict labels that humans\n can't assign. If a human can't be trained to assign labels by looking at the\n video for 1-2 seconds, the model likely can't be trained to do it either.\n\n- The model works best when there are at most 100 times more videos for the\n most common label than for the least common label. We recommend removing low\n frequency labels. For video classification, the recommended number of training\n videos per label is about 1,000. The minimum per label is 10, or 50 for advanced\n models. In general, it takes more examples per label to train models with\n multiple labels per video, and resulting scores are harder to interpret.\n\nSchema files\n------------\n\n- Use the following publicly accessible schema file when creating the\n jsonl file for importing annotations. This schema file dictates the format of\n the data input files. The structure of the file follows the\n [OpenAPI Schema](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#schema)\n test.\n\n **Video classification schema file**:\n\n [gs://google-cloud-aiplatform/schema/dataset/ioformat/video_classification_io_format_1.0.0.yaml](https://storage.cloud.google.com/google-cloud-aiplatform/schema/dataset/ioformat/video_classification_io_format_1.0.0.yaml)\n\n \u003cbr /\u003e\n\n #### **Full schema file**\n\n ```\n\n\n title: VideoClassification\n description: \u003e\n Import and export format for importing/exporting videos together with\n classification annotations with time segment. Can be used in\n Dataset.import_schema_uri field.\n type: object\n required:\n - videoGcsUri\n properties:\n videoGcsUri:\n type: string\n description: \u003e\n A Cloud Storage URI pointing to a video. Up to 50 GB in size and\n up to 3 hours in duration. Supported file mime types: `video/mp4`,\n `video/avi`, `video/quicktime`.\n timeSegmentAnnotations:\n type: array\n description: \u003e\n Multiple classification annotations. Each on a time segment of the video.\n items:\n type: object\n description: Annotation with a time segment on media (e.g., video).\n properties:\n displayName:\n type: string\n description: \u003e\n It will be imported as/exported from AnnotationSpec's display name.\n startTime:\n type: string\n description: \u003e\n The start of the time segment. Expressed as a number of seconds as\n measured from the start of the video, with \"s\" appended at the end.\n Fractions are allowed, up to a microsecond precision.\n default: 0s\n endTime:\n type: string\n description: \u003e\n The end of the time segment. Expressed as a number of seconds as\n measured from the start of the video, with \"s\" appended at the end.\n Fractions are allowed, up to a microsecond precision, and \"Infinity\"\n is allowed, which corresponds to the end of the video.\n default: Infinity\n annotationResourceLabels:\n description: Resource labels on the Annotation.\n type: object\n additionalProperties:\n type: string\n dataItemResourceLabels:\n description: Resource labels on the DataItem.\n type: object\n additionalProperties:\n type: string\n ```\n\n \u003cbr /\u003e\n\nInput files\n-----------\n\nThe format of your training data for video classification are as follows.\n| **Note:** When manually managing which videos are used for training or test purposes, be sure each instance of a video in the dataset has been assigned the *same* designation. If there's a contradiction, the dataset reverts to random assignments.\n\nTo import your data, create either a JSONL or CSV file.\n\n\u003cbr /\u003e\n\n### JSONL\n\nJSON on each line: \n\nSee [Classification schema (global)](/vertex-ai/docs/training-overview#video_data) file for details.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n```\n\n\n{\n\t\"videoGcsUri\": \"gs://bucket/filename.ext\",\n\t\"timeSegmentAnnotations\": [{\n\t\t\"displayName\": \"LABEL\",\n\t\t\"startTime\": \"start_time_of_segment\",\n\t\t\"endTime\": \"end_time_of_segment\"\n\t}],\n\t\"dataItemResourceLabels\": {\n\t\t\"aiplatform.googleapis.com/ml_use\": \"train|test\"\n\t}\n}\n```\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n#### Example JSONL - Video classification:\n\n```\n\n\n{\"videoGcsUri\": \"gs://demo/video1.mp4\", \"timeSegmentAnnotations\": [{\"displayName\": \"cartwheel\", \"startTime\": \"1.0s\", \"endTime\": \"12.0s\"}], \"dataItemResourceLabels\": {\"aiplatform.googleapis.com/ml_use\": \"training\"}}\n{\"videoGcsUri\": \"gs://demo/video2.mp4\", \"timeSegmentAnnotations\": [{\"displayName\": \"swing\", \"startTime\": \"4.0s\", \"endTime\": \"9.0s\"}], \"dataItemResourceLabels\": {\"aiplatform.googleapis.com/ml_use\": \"test\"}}\n...\n```\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n### CSV\n\n\nFormat of a row in the CSV:\n\n\u003cbr /\u003e\n\n```\n[ML_USE,]VIDEO_URI,LABEL,START,END\n```\n\n**List of columns**\n\n1. `ML_USE` (Optional). For data split purposes when training a model. Use TRAINING or TEST.\n2. `VIDEO_URI`. This field contains the Cloud Storage URI for the video. Cloud Storage URIs are case-sensitive.\n3. `LABEL`. Labels must start with a letter and only contain letters, numbers, and underscores. You can specify multiple labels for a video by adding multiple rows in the CSV file that each identify the same video segment, with a different label for each row.\n4. `START,END`. These two columns, START and END, respectively, identify the start and end time of the video segment to analyze, in seconds. The start time must be less than the end time. Both values must be non-negative and within the time range of the video. For example, `0.09845,1.36005`. To use the entire content of the video, specify a start time of `0` and an end time of the full-length of the video or \"inf\". For example, `0,inf`.\n\n#### Example CSV - Classification using single label\n\nSingle-label on the same video segment: \n\n```\nTRAINING,gs://YOUR_VIDEO_PATH/vehicle.mp4,mustang,0,5.4\n...\n```\n\n#### Example CSV - multiple labels:\n\nMulti-label on the same video segment: \n\n```\ngs://YOUR_VIDEO_PATH/vehicle.mp4,fiesta,0,8.285\ngs://YOUR_VIDEO_PATH/vehicle.mp4,ranger,0,8.285\ngs://YOUR_VIDEO_PATH/vehicle.mp4,explorer,0,8.285\n...\n```\n\n#### Example CSV - no labels:\n\n\nYou can also provide videos in the data file *without* specifying\nany labels. You must then use the Google Cloud console to apply labels to\nyour data before you train your model. To do so, you only need to\nprovide the Cloud Storage URI for the video followed by three commas,\nas shown in the following example. \n\n```\ngs://YOUR_VIDEO_PATH/vehicle.mp4,,,\n...\n```"]]