Stay organized with collections
Save and categorize content based on your preferences.
You can access the Looker IDE through the Looker Develop menu. See Accessing project files for details and other options.
The Looker IDE supports folders for your project files. Folders are shown in the left navigation pane of the IDE.
If your Looker project isn't organized into folders, your project will have a flat file structure, with files listed alphabetically in the File Browser panel. See Organizing an existing project with IDE folders for information on updating your project to use IDE folders.
The Looker IDE persists your currently open file and the expanded or collapsed status of the File Browser panel. You can reset the persistence in the IDE Settings.
If you import a project, the Looker IDE automatically creates an imported_projects folder. Files from both local projects and remote projects are listed in the imported_projects folder. Select an imported project file from the list of files in the imported_projects to view that file's contents.
Because they cannot be edited, imported project files are not visible when you are bulk-editing files in the IDE to move or delete those files.
Organizing an existing project with IDE folders
If your project previously had the legacy flat file structure or if you want to reorganize the files in a folder, you can choose to keep this structure; but if you choose to organize your project files into folders, we strongly recommend that you make the following preparations:
Plan the file structure ahead of time with all developers.
Ensure that all your Looker developers have deployed all their updates to production. If a developer has undeployed changes, their branch(es) will reflect the file structure that existed when they last pulled from production. If the project had a flat file structure at that time, the developer's version of the file will be pushed to production in its original location, so you will end up with two copies of the file. In addition, if a developer has undeployed changes during the migration to folders, that developer will face a merge conflict when they pull from production after the migration.
Enact a temporary code freeze with all your developers until the project has been fully migrated to the new directory structure.
Assign a single developer to move the files. The following procedure assumes a single developer will be migrating the project to IDE folders. If you need to have multiple developers move files, divide the task among the developers to avoid merge conflicts. If you do encounter merge conflicts, see the Using version control and deploying documentation page for information on resolving them.
Once all your developers have pushed and committed their changes and paused all work on the project, you can then migrate the project to its new directory structure.
Assign a single developer to do all the following steps:
Verify that all updates on all development branches have been deployed to production. This includes the development branches of the developer performing the migration to IDE folders.
Verify that all other developers have stopped making changes to the project.
Validate the project's LookML. It is expected that you will have multiple LookML errors and warnings, since the include and map_layer statements use references to file locations that likely will have been moved during this procedure.
Update any include and map_layer statements in your project to match the file's new path. In addition, you may see LookML validation errors for referenced objects that can no longer be found because their file paths have changed. For more information, see the documentation on using include with IDE folders and on using map_layer with IDE folders.
[[["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-25 UTC."],[],[],null,["# Working with the IDE file browser\n\nYou can access the Looker IDE through the Looker **Develop** menu. See [Accessing project files](/looker/docs/2512/accessing-project-files) for details and other options.\n\nThe Looker IDE supports folders for your project files. Folders are shown in the left navigation pane of the IDE.\n\nIf your Looker project isn't organized into folders, your project will have a flat file structure, with files listed alphabetically in the **File Browser** panel. See [Organizing an existing project with IDE folders](#organizing_an_existing_project_with_ide_folders) for information on updating your project to use IDE folders.\n\nThe Looker IDE persists your currently open file and the expanded or collapsed status of the **File Browser** panel. You can reset the persistence in the [**IDE Settings**](/looker/docs/2512/looker-ide#reset-layout).\n\nYou can select the icons in the toolbar at the top of the **File Browser** panel to collapse all folders, [move](/looker/docs/2512/creating-project-files#moving_files_and_folders_in_bulk) and [delete](/looker/docs/2512/creating-project-files#deleting_files_and_folders_in_bulk) files and folders, [search for a project file](/looker/docs/2512/accessing-project-files#searching_for_and_jumping_to_lookml_objects_or_project_files), or create [new folders](/looker/docs/2512/creating-project-files#creating_folders) and [new files](/looker/docs/2512/creating-project-files#creating_files).\n\nImported projects folder\n------------------------\n\nIf you [import a project](/looker/docs/2512/importing-projects), the Looker IDE automatically creates an `imported_projects` folder. Files from both [local projects](/looker/docs/2512/importing-projects#specifying_local_projects) and [remote projects](/looker/docs/2512/importing-projects#specifying_remote_projects) are listed in the `imported_projects` folder. Select an imported project file from the list of files in the `imported_projects` to view that file's contents.\n\nBecause they cannot be edited, imported project files are not visible when you are bulk-editing files in the IDE to [move](/looker/docs/2512/creating-project-files#moving_files_and_folders_in_bulk) or [delete](/looker/docs/2512/creating-project-files#moving_files_and_folders_in_bulk) those files.\n\n\nOrganizing an existing project with IDE folders\n-----------------------------------------------\n\nIf your project previously had the legacy flat file structure or if you want to reorganize the files in a folder, you can choose to keep this structure; but if you choose to organize your project files into folders, we strongly recommend that you make the following preparations:\n\n- Plan the file structure ahead of time with all developers.\n- Ensure that all your Looker developers have [deployed all their updates to production](/looker/docs/2512/version-control-and-deploying-changes#deploying_to_production). If a developer has undeployed changes, their branch(es) will reflect the file structure that existed when they last [pulled from production](/looker/docs/2512/git-command-reference#pull_prod). If the project had a flat file structure at that time, the developer's version of the file will be pushed to production in its original location, so you will end up with two copies of the file. In addition, if a developer has undeployed changes during the migration to folders, that developer will face a merge conflict when they pull from production after the migration.\n- Enact a temporary code freeze with all your developers until the project has been fully migrated to the new directory structure.\n- Assign a single developer to move the files. The following procedure assumes a single developer will be migrating the project to IDE folders. If you need to have multiple developers move files, divide the task among the developers to avoid merge conflicts. If you do encounter merge conflicts, see the [Using version control and deploying](/looker/docs/2512/version-control-and-deploying-changes#resolving_merge_conflicts) documentation page for information on resolving them.\n\n| **Note:** Be aware that when you move a file in Git, you are effectively deleting the file and creating a new file with a new path. This means that the Git history for the file will be empty, because Git will consider it a new file. To see the file's Git history before it was moved, use your Git interface to navigate to the file in its original location and view the Git history from there.\n\nOnce all your developers have pushed and committed their changes and paused all work on the project, you can then migrate the project to its new directory structure.\n\nAssign a single developer to do all the following steps:\n\n1. Verify that all updates on all development branches have been [deployed to production](/looker/docs/2512/version-control-and-deploying-changes#deploying_to_production). This includes the development branches of the developer performing the migration to IDE folders.\n2. Verify that all other developers have stopped making changes to the project.\n3. [Pull from production](/looker/docs/2512/git-command-reference#pull_prod).\n4. [Create the project's folders](/looker/docs/2512/creating-project-files#creating_folders).\n5. Move the project files into the folders, either [one file at a time](/looker/docs/2512/creating-project-files#moving_items_in_a_foldered_project) or [using bulk edit](/looker/docs/2512/creating-project-files#moving_files_and_folders_in_bulk).\n6. [Validate the project's LookML](/looker/docs/2512/lookml-validation#validating_your_lookml). It is expected that you will have multiple LookML errors and warnings, since the `include` and `map_layer` statements use references to file locations that likely will have been moved during this procedure.\n7. Update any `include` and `map_layer` statements in your project to match the file's new path. In addition, you may see LookML validation errors for referenced objects that can no longer be found because their file paths have changed. For more information, see the documentation on [using `include` with IDE folders](/looker/docs/2512/reference/param-model-include#using_include_with_ide_folders) and on [using `map_layer` with IDE folders](/looker/docs/2512/reference/param-model-map-layer#using_map_layer_with_ide_folders).\n\n | **Tip:** You can use [wildcards](/looker/docs/2512/reference/param-model-include#wildcard_examples) to create a temporary fix for LookML validation warnings and errors resulting from `include` statements. Using view files as an example, you can specify `include: \"/**/*.view\"` to include all files in all your project folders. This will prevent LookML validation problems while you continue developing. However, this is not a recommended solution for the long term, since including more files than are needed can [affect performance](/looker/docs/2512/reference/param-model-include#including_all_view_files_can_affect_performance).\n\n \u003cbr /\u003e\n\n8. [Commit the changes](/looker/docs/2512/version-control-and-deploying-changes#committing_changes).\n\n9. [Deploy the updates to production](/looker/docs/2512/version-control-and-deploying-changes#deploying_to_production).\n\n10. Inform the other Looker developers that they can now [pull the updates from production](/looker/docs/2512/git-command-reference#pull_prod) and resume developing in the project."]]
