The label parameter helps make Explores more user-friendly by allowing you to set the view names that appear in the field picker. If not specified, the label defaults to the name of the view.
Example
In the field picker, make the view appear as Product ID Info for a view named product_id_information:
view: product_id_information {
label: "Product ID Info"
}
Things to consider
A label does not change LookML references
The label affects only the displayed name of the view in the Explore; the label does not affect how you refer to the view in LookML. Views with labels are still referenced with the normal ${view_name.field_name} syntax in your LookML files.
A label isn't necessary if you name views thoughtfully
A view does not need a label parameter if the name already appears and is formatted how you want your users to see it in the field picker. If you know how you want a view to appear to your users, you can often consider this when naming it, avoiding the need to use label.
Typically label is only used when you want to perform one of the following tasks:
Change the way that a view name is formatted. For example, you can make the view name "abc_info" appear as "ABC Info" instead of "Abc Info"
Create two different views with different dimensions and measures that are based on the same SQL table
[[["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-14 UTC."],[],[],null,["# label (for views)\n\n\u003cbr /\u003e\n\n\u003e This page refers to the `label` parameter that is part of a [view](/looker/docs/2512/reference/param-view).\n\u003e\n\u003e `label` can also be used as part of a model, described on the [Model parameters](/looker/docs/2512/reference/param-model) documentation page.\n\u003e\n\u003e `label` can also be used as part of an Explore, described on the [`label` (for Explores)](/looker/docs/2512/reference/param-explore-label) parameter documentation page.\n\u003e\n\u003e `label` can also be used as part of a field, described on the[`label` (for fields)](/looker/docs/2512/reference/param-field-label) parameter documentation page.\n\u003e\n\u003e `label` can also be used as part of a reference line, described on the [Dashboard reference line parameters](/looker/docs/2512/reference/param-lookml-dashboard-reference-line) documentation page.\n\nUsage\n-----\n\n```\nview: view_name {\n label: \"desired label for the view\"\n}\n```\n\nDefinition\n----------\n\nThe `label` parameter helps make Explores more user-friendly by allowing you to set the view names that appear in the [field picker](/looker/docs/2512/changing-explore-menu-and-field-picker). If not specified, the label defaults to the name of the view.\n\nExample\n-------\n\nIn the field picker, make the view appear as **Product ID Info** for a view named `product_id_information`: \n\n view: product_id_information {\n label: \"Product ID Info\"\n }\n\n\nThings to consider\n------------------\n\n### A `label` does not change LookML references\n\nThe label affects only the displayed name of the view in the Explore; the label does not affect how you refer to the view in LookML. Views with labels are still referenced with the normal `${view_name.field_name}` syntax in your LookML files.\n\n\n### A `label` can affect multiple Explores\n\nUnlike [view_label (for Explores)](/looker/docs/2512/reference/param-explore-view-label) and [view_label (for joins)](/looker/docs/2512/reference/param-explore-join-view-label), this parameter affects all Explores that use the view.\n\n### A `label` isn't necessary if you name views thoughtfully\n\nA view does not need a `label` parameter if the name already appears and is formatted how you want your users to see it in the field picker. If you know how you want a view to appear to your users, you can often consider this when naming it, avoiding the need to use `label`.\n\nTypically `label` is only used when you want to perform one of the following tasks:\n\n- Change the way that a view name is formatted. For example, you can make the view name \"abc_info\" appear as \"ABC Info\" instead of \"Abc Info\"\n- Create two different views with different dimensions and measures that are based on the same SQL table"]]
