How to create a folder in SharePoint
In short
- To create a SharePoint folder, open the document library, select New and then Folder, enter a name, and select Create.
- SharePoint in Microsoft 365 limits the decoded file path, including the filename, to 400 characters, so long folder names leave less room below.
- If the Folder option is missing, a library owner can set Make New Folder command available to Yes under Library settings and Advanced settings.
- New folders inherit permissions from their parent, so naming a folder Confidential does not restrict access and you should review permissions before adding sensitive documents.
To create a folder in SharePoint, open the document library, select + New > Folder, enter a name, and select Create. You can then add files or create subfolders inside it. Below, you’ll find the manual steps, troubleshooting checks, planning tips, and options for automating repeatable folder structures. (support.microsoft.com)
How do you create a folder in a SharePoint document library?
Create a folder from the document library where you want it stored—not from the site’s page editor. Open an existing folder first if you want the new folder nested inside it. (support.microsoft.com)
- Open your SharePoint site and navigate to the relevant document library.
- Choose the destination. Stay at the library’s top level or open a parent folder.
- Select + New, then choose Folder.
- Enter a descriptive name, such as Project Atlas.
- Select Create to save the folder. (support.microsoft.com)
Before continuing, confirm that the location matches your intention. For example, a project folder intended for shared delivery work should not accidentally sit inside another project’s archive. Make this location check part of your routine, especially when working across several libraries.
Prepare access and folder names before adding files
You need permission to add content to the destination library. SharePoint permission levels determine available actions, so being able to view documents does not necessarily mean you can create folders. If your access is read-only, ask the library owner to review the permissions you need. (learn.microsoft.com)
Choose names that explain the contents without becoming miniature descriptions. A useful convention might combine a project identifier and short name, such as PRJ-104 Atlas. Agree on the pattern before colleagues start creating their own variations.
Keep these naming checks handy:
- Avoid unsupported characters: Examples include quotation marks, asterisks, colons, angle brackets, question marks, slashes, backslashes, and vertical bars.
- Avoid leading or trailing spaces: These are not allowed in folder names.
- Keep the whole path manageable: SharePoint in Microsoft 365 limits the decoded file path, including the filename, to 400 characters. Long folder names consume space needed by files farther down the hierarchy. (support.microsoft.com)
Prefer Contracts over a label such as All Contracts and Related Contract Documentation. The shorter option leaves room for meaningful filenames and is easier for colleagues to recognize.
Does a folder appear immediately after creation in SharePoint?
After successful creation, the folder should appear in its document library. Microsoft recommends refreshing the browser if you do not see it. For an automated process, distinguish between starting the workflow and completing the folder-creation action: SharePoint triggers can check periodically for changes rather than running instantly. (support.microsoft.com)
Before trying to create the same folder again, work through this checklist:
- Recheck the destination: Confirm the site, library, and parent folder you used.
- Refresh the library: Look again before assuming the operation failed.
- Read any error message: Record its wording rather than repeatedly submitting the same request.
- For automation, inspect the run: Establish whether folder creation actually completed before investigating visibility.
Treat these as diagnostic checks, not evidence that the folder has disappeared. If you ask an administrator for help, provide the intended location, folder name, creation method, and error text. That gives them a concrete starting point.
Fix a missing Folder option
If Folder is missing from the + New menu, folder creation may be disabled. A library owner or someone with design permissions can open Settings > Library settings > Advanced settings and set Make “New Folder” command available to Yes. (support.microsoft.com)
Separate a missing command from an access problem. The first concerns the library’s configuration; the second concerns what your account is allowed to do. Ask the owner to check both rather than requesting broader access than your work requires. (support.microsoft.com)
Build a SharePoint folder structure people can follow
Plan your SharePoint folder structure around how people retrieve documents. Start with the organizing principle that matters most—perhaps client, project, or business function—and use it consistently. Avoid introducing a new level unless it helps someone decide where a document belongs.
For example, a proposed project structure could use:
| Folder | Intended contents |
|---|---|
| Projects/PRJ-104 Atlas/Planning | Briefs, schedules, and working plans |
| Projects/PRJ-104 Atlas/Delivery | Working deliverables and review material |
| Projects/PRJ-104 Atlas/Approved | Documents your team has confirmed as approved |
| Projects/PRJ-104 Atlas/Archive | Material no longer needed for active work |
These are suggested labels, not SharePoint status controls. Define what qualifies as “Approved” and who moves material there; the folder name alone should not be your approval process.
Before adopting the structure, test it with a few real documents. Ask two colleagues where they would save each one. If their answers differ, clarify the categories before creating more SharePoint folders.
Also consider views instead of adding another folder level. SharePoint views can filter, group, and sort content, and Microsoft notes that a combination of views and folders may suit larger libraries. (support.microsoft.com)
How can you automate folder creation in SharePoint?
You can automate folder creation in SharePoint with Power Automate’s Create new folder action. It accepts a site address, a list or library, and a folder path, allowing a workflow to create a folder or nested path. This is useful when you want a repeatable setup rather than manually building each project workspace. (learn.microsoft.com)
Create repeatable folders with Power Automate
For a project-intake scenario, start with an automated cloud flow using SharePoint’s When an item is created trigger. Configure it against the list that records new projects. This separates the project request from the library where its documents will live. (learn.microsoft.com)
Then configure the folder action:
- Add Create new folder from the SharePoint connector.
- Set Site Address to the destination site.
- Choose List or Library for the destination document library.
- Set Folder Path to a relative path such as Projects/PRJ-104 Atlas/Planning.
- Use values from the triggering item where the project identifier or name should vary. (learn.microsoft.com)
For a SharePoint automated folder creation process, write down the desired outcome before adding more actions. Decide which subfolders every project needs, how names are validated, and what should happen if someone submits the project twice. Test with a sample record and verify the resulting location before using real intake data.
Use a folder structure creation script for SharePoint
For administrator-led provisioning, a folder structure creation script for SharePoint is another option. PnP PowerShell provides commands for creating folders, while its connection options support authenticated access to your site. Configure an approved application and appropriate access before running provisioning commands. (pnp.github.io)
After establishing the connection, Add-PnPFolder -Name "Planning" -Folder "Shared Documents/Projects/PRJ-104 Atlas" illustrates creating a folder beneath an existing parent. Replace the example path with the actual location in your library. (pnp.github.io)
For repeatable path provisioning, Resolve-PnPFolder -SiteRelativePath "Shared Documents/Projects/PRJ-104 Atlas/Planning" returns the folder and creates it if it does not exist. This behavior can help when rerunning a setup process. Test against a nonproduction location before expanding the script to multiple projects. (pnp.github.io)
Check permissions before calling the folder ready
New folders normally inherit permissions from their parent location. Creating a folder does not automatically establish a separate security boundary, so a name such as Confidential is not an access restriction. Review permissions before placing sensitive documents inside. (support.microsoft.com)
Use your organization’s established access model and involve the library owner when exceptions are necessary. Microsoft recommends managing team-site permissions through the associated Microsoft 365 group and using built-in SharePoint groups for communication sites. Avoid making unique folder permissions your default organizational method. (support.microsoft.com)
Keep the setup simple and repeatable
Start with one clearly named folder in the correct library, then check its location and access before adding documents. Agree on a practical structure before multiplying it across projects. When repetition becomes the problem, choose a tested flow or script—and keep the same naming and ownership rules behind both manual and automated creation.
Related guides
Sources
- Create a folder in a document library | Microsoft Support
- Understanding permission levels in SharePoint - SharePoint in Microsoft 365 | Microsoft Learn
- Restrictions and limitations in OneDrive and SharePoint | Microsoft Support
- SharePoint - Connectors | Microsoft Learn
- Create and test an approval workflow with Power Automate - Power Automate | Microsoft Learn
- Add-PnPFolder | PnP PowerShell
- Resolve-PnPFolder | PnP PowerShell
- Customize permissions for a SharePoint list or library | Microsoft Support