Labels overview
Stay organized with collections
Save and categorize content based on your preferences.
Labels are metadata that you define to help users organize, find, and apply
policy to files in Google Drive. The Drive API allows developers to
apply labels to files and folders, set label field values, read labels and field
values on files, and search for files using metadata terms defined by the custom
label taxonomy.
Drive labels can support business processes by attaching metadata
to files and folders. Common uses for labels are:
Classify content to follow an information governance strategy—Create a
label to identify sensitive content or data that requires special handling.
For example, you might create a badged label (a label with color-coded
option values) titled "Sensitivity" with the values of "Top Secret,"
"Confidential," and "Public."
Apply policy to items in Drive—Create labels to manage
Drive content throughout its lifecycle and ensure it adheres
to your organization's record keeping practices. For example, use labels to
manage a data loss policy (DLP) whereby users can't download files with a
"Sensitivity" label set to "Top Secret".
Curate and find files—Create labels to increase searchability of your
company's content by letting people in your organization find items based on
labels and their fields. For example, apply a "Signature Status" label set
to "Awaiting Signature" to all contracts awaiting signature by a specific
date. Drive search can then return these contracts when
someone searches "awaiting signature".
Below is a list of common terms used by Drive labels:
- Label
Structured metadata placed on a Drive file.
Drive users can assign labels and set label field values
for files. Labels are composed of:
- Label name
- The resource name of the label. The label ID is part of the
Label name. Depending on the request, the name is in the form of either:
labels/{id}
or labels/{id}@{revisionId}
. For more information, see
Label revision below.
- Label ID
- A globally unique identifier for the label. The ID is part of the
label name, but unlike the name, it's consistent between revisions.
- Field
An individual typed, settable component of a label. A label can have zero or
more fields associated with it. Selection and user fields can be set with
multiple values if the field is configured with
ListOptions
in the
Google Drive Labels API.
- Field type
- The data type of the value associated with the field. Configurable as
integer, dateString, text, user, or selection. The type chosen impacts
both the valid values applicable to Drive items and the
search query options available.
- Label taxonomy
The configured label fields available to users for application to
Drive files. Readable and writable through the
Drive Labels API. Also known as the label schema.
- Label revision
An instance of the label. Anytime a label is created, updated, published, or
deprecated, the label revision increments.
- Draft revision
- The revision number of the current draft instance of the label. You can
make several updates to a label, each incrementing its draft revision
number, without affecting the published revision. The ability to have
draft labels lets you test label updates before publishing.
- Published revision
- The revision number of the published version of a label. The published
label is the instance of the label available to users.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-28 UTC.
[null,null,["Last updated 2025-08-28 UTC."],[],[],null,["# Labels overview\n\n*Labels* are metadata that you define to help users organize, find, and apply\npolicy to files in Google Drive. The Drive API allows developers to\napply labels to files and folders, set label field values, read labels and field\nvalues on files, and search for files using metadata terms defined by the custom\nlabel taxonomy.\n\nDrive labels can support business processes by attaching metadata\nto files and folders. Common uses for labels are:\n\n- **Classify content to follow an information governance strategy**---Create a\n label to identify sensitive content or data that requires special handling.\n For example, you might create a badged label (a label with color-coded\n option values) titled \"Sensitivity\" with the values of \"Top Secret,\"\n \"Confidential,\" and \"Public.\"\n\n- **Apply policy to items in Drive**---Create labels to manage\n Drive content throughout its lifecycle and ensure it adheres\n to your organization's record keeping practices. For example, use labels to\n manage a data loss policy (DLP) whereby users can't download files with a\n \"Sensitivity\" label set to \"Top Secret\".\n\n- **Curate and find files**---Create labels to increase searchability of your\n company's content by letting people in your organization find items based on\n labels and their fields. For example, apply a \"Signature Status\" label set\n to \"Awaiting Signature\" to all contracts awaiting signature by a specific\n date. Drive search can then return these contracts when\n someone searches \"awaiting signature\".\n\nBelow is a list of common terms used by Drive labels:\n\n*Label*\n\n: Structured metadata placed on a Drive file.\n Drive users can assign labels and set label field values\n for files. Labels are composed of:\n\n *Label name*\n : The resource name of the label. The *label ID* is part of the\n Label name. Depending on the request, the name is in the form of either:\n `labels/{id}` or `labels/{id}@{revisionId}`. For more information, see\n [Label revision](#revision) below.\n\n *Label ID*\n : A globally unique identifier for the label. The ID is part of the\n label name, but unlike the name, it's consistent between revisions.\n\n*Field*\n\n: An individual typed, settable component of a label. A label can have zero or\n more fields associated with it. Selection and user fields can be set with\n multiple values if the field is configured with\n [`ListOptions`](/workspace/drive/labels/reference/rest/v2/labels#listoptions) in the\n [Google Drive Labels API](/workspace/drive/labels/guides/overview).\n\n *Field type*\n : The data type of the value associated with the *field*. Configurable as\n integer, dateString, text, user, or selection. The type chosen impacts\n both the valid values applicable to Drive items and the\n search query options available.\n\n*Label taxonomy*\n\n: The configured label fields available to users for application to\n Drive files. Readable and writable through the\n Drive Labels API. Also known as the label schema.\n\n*Label revision*\n\n: An instance of the label. Anytime a label is created, updated, published, or\n deprecated, the label revision increments.\n\n *Draft revision*\n : The revision number of the current draft instance of the label. You can\n make several updates to a label, each incrementing its draft revision\n number, without affecting the published revision. The ability to have\n draft labels lets you test label updates before publishing.\n\n *Published revision*\n : The revision number of the published version of a label. The published\n label is the instance of the label available to users.\n\nRelated topics\n--------------\n\n- To learn about using labels in Drive, see [Set a label field\n on a file](/workspace/drive/api/guides/set-label).\n- Learn more about the [Drive Labels API](/workspace/drive/labels/guides/overview)."]]