The mkdir command in Linux creates new directories. Its basic form is mkdir DIRECTORY, and you can create multiple folders at once, set permissions with -m, build nested paths with -p, and print output with -v. <\/p>\n\n\n\n
It respects your umask, returns errors if a path exists without -p, and supports advanced patterns like brace expansion. Creating directories is one of the first things you do on any Linux system. <\/p>\n\n\n\n
In this guide, we\u2019ll explain the mkdir command in Linux with clear examples, best practices, and troubleshooting tips. By the end, you\u2019ll confidently create single, multiple, and nested directories with the right permissions, whether locally or on a server at YouStable.<\/p>\n\n\n\n
mkdir (make directory) is a core Linux utility that creates one or more directories. It\u2019s part of GNU coreutils on most distributions and is also available in BSD variants (macOS). It\u2019s often used in deployment scripts, CI\/CD pipelines<\/a>, and everyday file management.<\/p>\n\n\n\n Here\u2019s the standard syntax and the options you\u2019ll use most:<\/p>\n\n\n\n If \u201creports\u201d already exists, mkdir returns an error unless you use -p (explained below).<\/p>\n\n\n\n This creates three directories in the current working path. You can also use absolute paths.<\/p>\n\n\n\n Use -p to create parent directories as needed and avoid errors if paths already exist.<\/p>\n\n\n\n Brace expansion ({…}) is handled by your shell (e.g., bash), not mkdir. It expands into three directories under \/var\/www\/project.<\/p>\n\n\n\n By default, new directory permissions are influenced by your umask. Typical defaults are 022 or 002 depending on the distro and policy. You can check your current umask with:<\/p>\n\n\n\n Note: <\/strong>The -m value overrides the default umask for that command only. If you need to adjust defaults system wide, modify your shell or PAM configuration, then relogin.<\/p>\n\n\n\n Absolute paths start from \/ and are unambiguous (\/data\/backups). Relative paths depend on your current directory (.\/backups or just backups). For scripts and automation, prefer absolute paths to reduce errors.<\/p>\n\n\n\n mkdir provides helpful errors. Here are common ones and quick fixes:<\/p>\n\n\n\nSyntax and Common Options<\/h3>\n\n\n\n
mkdir [OPTIONS] DIRECTORY [DIRECTORY...]\n# Common options:\n# -p, --parents Create parent directories as needed, no error if existing\n# -m, --mode=MODE Set permissions on the new directory (e.g., 755 or u=rwx,go=rx)\n# -v, --verbose Print a message for each created directory\n# -Z, --context=CTX Set SELinux security context (on SELinux-enabled systems)<\/code><\/pre>\n\n\n\n
\n\n\n\nBasic Usage Examples<\/h2>\n\n\n\n
Create a Single Directory<\/h3>\n\n\n\n
mkdir reports<\/code><\/pre>\n\n\n\nCreate Multiple Directories at Once<\/h3>\n\n\n\n
mkdir january february march<\/code><\/pre>\n\n\n\nCreate Nested Directories with -p<\/h3>\n\n\n\n
mkdir -p \/var\/www\/project\/{public,logs,backup}<\/code><\/pre>\n\n\n\n
\n\n\n\nSetting Permissions with -m (and Understanding umask)<\/h2>\n\n\n\n
umask<\/code><\/pre>\n\n\n\nSet Numeric Permissions<\/h3>\n\n\n\n
# 755 = owner rwx, group rx, others rx\nmkdir -m 755 app\n\n# 700 = owner rwx only\nmkdir -m 700 secrets<\/code><\/pre>\n\n\n\nSet Symbolic Permissions<\/h3>\n\n\n\n
mkdir -m u=rwx,go=rx shared\nmkdir -m u=rwx,g=rx,o= private_team<\/code><\/pre>\n\n\n\n
\n\n\n\nVerbose Output and Absolute vs. Relative Paths<\/h2>\n\n\n\n
Use -v to Confirm What\u2019s Created<\/h3>\n\n\n\n
mkdir -vp \/opt\/tools\/bin\n# Output: mkdir: created directory '\/opt\/tools'\n# mkdir: created directory '\/opt\/tools\/bin'<\/code><\/pre>\n\n\n\nAbsolute vs. Relative Paths<\/h3>\n\n\n\n
\n\n\n\nHandling Errors: File Exists, Permission Denied, and More<\/h2>\n\n\n\n
\n
# Robust pattern for idempotent script runs\nmkdir -p \/srv\/app\/logs || { echo \"Failed to create logs\"; exit 1; }<\/code><\/pre>\n\n\n\nReal World Use Cases (Hosting and DevOps)<\/h2>\n\n\n\n
\n