[[["์ดํดํ๊ธฐ ์ฌ์","easyToUnderstand","thumb-up"],["๋ฌธ์ ๊ฐ ํด๊ฒฐ๋จ","solvedMyProblem","thumb-up"],["๊ธฐํ","otherUp","thumb-up"]],[["์ดํดํ๊ธฐ ์ด๋ ค์","hardToUnderstand","thumb-down"],["์๋ชป๋ ์ ๋ณด ๋๋ ์ํ ์ฝ๋","incorrectInformationOrSampleCode","thumb-down"],["ํ์ํ ์ ๋ณด/์ํ์ด ์์","missingTheInformationSamplesINeed","thumb-down"],["๋ฒ์ญ ๋ฌธ์ ","translationIssue","thumb-down"],["๊ธฐํ","otherDown","thumb-down"]],["์ต์ข ์ ๋ฐ์ดํธ: 2025-09-03(UTC)"],[],[],null,["# About folders in buckets with hierarchical namespace enabled\n\nThis page provides information about folders in buckets with\nhierarchical namespace enabled.\n\nOverview\n--------\n\nFolders exist as a resource in buckets with [hierarchical namespace](/storage/docs/hns-overview)\nenabled. You can organize objects within folders in a file system-like\nstructure. Cloud Storage provides folder management APIs that enable\noperations such as creating, deleting, renaming, and listing folders, as well as\nretrieving folder metadata.\n\nFolder metadata\n---------------\n\nA folder's metadata contains structured information about the folder. For\ndetailed information about folder metadata, see the [`Folder` resource](/storage/docs/json_api/v1/folders#resource) in\nthe Cloud Storage JSON API reference documentation.\n\nThe key components of a folder metadata are as follows:\n\n- `bucket`: The name of the bucket where the folder resides. For example, `my-bucket`.\n- `id`: A unique identifier for the folder within the bucket. For example, `hns-bucket/dir1/`.\n- `kind`: The resource type. For a folder, this value is always `storage#folder`.\n- `name`: The name of the folder. For example, `dir1/`.\n- `selfLink`: A URL that references the folder in the Cloud Storage API.\n- `timeCreated`: The timestamp when the folder was created. For example, `2023-05-05T16:32:08.878000+00:00`.\n- `updated`: The timestamp when the folder was last updated. For example, `2024-05-06T16:32:08.878000+00:00`.\n\nConsiderations\n--------------\n\nWhen creating folders, consider the following:\n\n- **Object and folder names** : Buckets with hierarchical namespace enabled,\n support all valid [object names](/storage/docs/objects#naming), including\n those with leading, trailing slashes (`/`) or consecutive slashes. Each\n forward slash (`/`) in an object name represents a folder.\n The following table shows examples of the relationship between object names\n and their corresponding location in the folder hierarchy:\n\n- **Maximum folder depth** : Buckets with hierarchical namespace enabled\n support a maximum folder depth of 50. As a result, object names cannot have\n more than 50 slashes (`/`).\n\n- **Maximum folder name size**: 512 bytes (UTF-8 encoded).\n\n- **Automatic folder creation** : Creating a new object automatically creates\n any non-existent folders specified in the object's path. For example,\n creating an object named `dir1/foo.txt` automatically creates the folder\n `dir1/` if it doesn't already exist.\n\n- **Sensitive or personally identifiable information (PII)**: Folder names are\n more broadly visible than folder metadata. For example, folder names appear\n in URLs and when listing folders or objects in a bucket. Don't include\n sensitive information or PII in folder names.\n\nWhat's next\n-----------\n\n- [Create and manage folders](/storage/docs/create-folders).\n- [Rename a folder](/storage/docs/rename-hns-folders).\n- [Optimize folder management](/storage/docs/hns-buckets-best-practices#folder-management).\n\nTry it for yourself\n-------------------\n\n\nIf you're new to Google Cloud, create an account to evaluate how\nCloud Storage performs in real-world\nscenarios. New customers also get $300 in free credits to run, test, and\ndeploy workloads.\n[Try Cloud Storage free](https://console.cloud.google.com/freetrial)"]]
