{"id":6579,"date":"2026-04-29T08:35:01","date_gmt":"2026-04-29T12:35:01","guid":{"rendered":"https:\/\/www.globesign.com\/blog\/?p=6579"},"modified":"2026-04-29T17:19:29","modified_gmt":"2026-04-29T21:19:29","slug":"linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert","status":"publish","type":"post","link":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/","title":{"rendered":"Linux Filesystem Hierarchy Explained: The Complete Guide (Beginner to Expert)"},"content":{"rendered":"

You Opened a Linux Terminal. Now What?<\/strong><\/h2>\n

You typed ls \/<\/code> and got hit with a wall of folders \u2014 bin, boot, dev, etc, home, lib\u2026 and your brain said “nope.”<\/em><\/p>\n

Don’t worry. Every Linux user has been there.<\/p>\n

Here’s the truth: Linux’s filesystem isn’t random.<\/strong> It follows a beautiful, logical standard called the Filesystem Hierarchy Standard (FHS)<\/strong>. Once you understand it, navigating any Linux system \u2014 Ubuntu, Arch, Debian, a cloud server, a Raspberry Pi \u2014 feels like reading a map you already know.<\/p>\n

This guide breaks down every major directory, what lives there, why it exists, and when you’ll actually care about it.<\/p>\n

First: Everything Starts at \/<\/code> \u2014 The Root Directory<\/strong><\/h2>\n

Think of \/<\/code> (just a single forward slash) as the trunk of a tree<\/strong>. Every file, folder, and device on your entire Linux system hangs off this one point.<\/p>\n

There’s no C:\\<\/code> or D:\\<\/code> like Windows. There’s just \/<\/code>. One tree. One root. Everything branches from here.<\/p>\n

\n
\n
\n
\n
\"\"<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\/\r\n\u251c\u2500\u2500 bin\r\n\u251c\u2500\u2500 boot\r\n\u251c\u2500\u2500 dev\r\n\u251c\u2500\u2500 etc\r\n\u251c\u2500\u2500 home\r\n\u251c\u2500\u2500 lib & lib64\r\n\u251c\u2500\u2500 media\r\n\u251c\u2500\u2500 mnt\r\n\u251c\u2500\u2500 opt\r\n\u251c\u2500\u2500 proc\r\n\u251c\u2500\u2500 root\r\n\u251c\u2500\u2500 sbin\r\n\u251c\u2500\u2500 srv\r\n\u251c\u2500\u2500 usr\r\n\u2514\u2500\u2500 var\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n
Now let’s walk through each branch.<\/p>\n
\/bin<\/code> \u2014 The Basic Toolkit<\/strong><\/h3>\n
What it is:<\/strong> Essential command binaries (programs) that every user can run.<\/p>\n
What lives here:<\/strong> ls<\/code>, cp<\/code>, mv<\/code>, cat<\/code>, echo<\/code>, mkdir<\/code> \u2014 the everyday commands you use constantly.<\/p>\n
Think of it as:<\/strong> The toolbox that’s always within arm’s reach. Without \/bin<\/code>, you literally couldn’t do anything in a terminal.<\/p>\n
Real-world moment:<\/strong> When you type ls<\/code> to list files? That command is physically stored in \/bin\/ls<\/code>. You’re running a file every single time.<\/p>\n
\/boot<\/code> \u2014 The Ignition Switch<\/strong><\/h3>\n
What it is:<\/strong> Everything needed to start up<\/strong> the operating system.<\/p>\n
What lives here:<\/strong> The Linux kernel itself, initramfs<\/code> (initial RAM filesystem), and bootloader files (like GRUB).<\/p>\n
Think of it as:<\/strong> The key that starts the car. The system reads this directory before anything else is even loaded into memory.<\/p>\n
Pro tip:<\/strong> Unless you’re customizing your bootloader or kernel, don’t touch \/boot<\/code><\/strong>. Messing with it can make your system unbootable.<\/p>\n
\/dev<\/code> \u2014 The Device Whisperer<\/strong><\/h3>\n
What it is:<\/strong> Device files \u2014 Linux’s way of treating hardware as files.<\/p>\n
What lives here:<\/strong> Representations of hard drives (\/dev\/sda<\/code>), USB drives (\/dev\/sdb<\/code>), terminals (\/dev\/tty<\/code>), and even \/dev\/null<\/code> (the famous “trash void” of Linux).<\/p>\n
Think of it as:<\/strong> A control panel where every piece of hardware gets its own file handle.<\/p>\n
Mind-bending fact:<\/strong> In Linux, everything is a file<\/em> \u2014 including your keyboard, your screen, and your hard drive. \/dev<\/code> is where that philosophy becomes real.<\/p>\n
\/etc<\/code> \u2014 The System’s Brain<\/strong><\/h3>\n
What it is:<\/strong> System-wide configuration files.<\/p>\n
What lives here:<\/strong> Network settings, user account info (\/etc\/passwd<\/code>), SSH config, cron jobs, package manager settings \u2014 basically the settings menu for your entire OS.<\/p>\n
Think of it as:<\/strong> The control panel of a building. Everything that governs how the system behaves lives here.<\/p>\n
You’ll use this when:<\/strong> Setting up a web server, configuring SSH, changing hostnames, managing users, editing network interfaces. As a sysadmin, \/etc<\/code> is your second home.<\/p>\n
\/home<\/code> \u2014 Your Personal Space<\/strong><\/h3>\n
What it is:<\/strong> User home directories.<\/p>\n
What lives here:<\/strong> Every regular user gets their own folder here. If your username is ali<\/code>, your personal space is \/home\/ali<\/code> \u2014 your documents, downloads, desktop, configs, and dotfiles.<\/p>\n
Think of it as:<\/strong> Your bedroom in a shared apartment. Everyone else has one too, but yours is yours.<\/p>\n
Good to know:<\/strong> The ~<\/code> symbol in the terminal is a shortcut for your home directory. cd ~<\/code> takes you straight home, no matter where you are.<\/p>\n
\/lib<\/code> & \/lib64<\/code> \u2014 The Shared Libraries<\/strong><\/h3>\n
What it is:<\/strong> Essential shared libraries that core system programs need to run.<\/p>\n
What lives here:<\/strong> .so<\/code> files (shared objects) \u2014 the Linux equivalent of .dll<\/code> files on Windows. Programs in \/bin<\/code> and \/sbin<\/code> pull from here constantly.<\/p>\n
Think of it as:<\/strong> A common toolbox that multiple programs share instead of each carrying their own copies.<\/p>\n
64-bit systems<\/strong> have both \/lib<\/code> (32-bit) and \/lib64<\/code> (64-bit) because some software still needs both.<\/p>\n
\/media<\/code> \u2014 Plug It In<\/strong><\/h3>\n
What it is:<\/strong> Mount points for removable media.<\/p>\n
What lives here:<\/strong> When you plug in a USB drive or insert a CD, Linux automatically mounts it under \/media<\/code>. For example: \/media\/username\/USB_DRIVE<\/code>.<\/p>\n
Think of it as:<\/strong> The USB ports and disc trays of your filesystem.<\/p>\n
Modern desktops<\/strong> handle this automatically. You plug in a drive, it shows up in \/media<\/code>, you eject it, it disappears. Clean and simple.<\/p>\n
\/mnt<\/code> \u2014 The Manual Dock<\/strong><\/h3>\n
What it is:<\/strong> Temporary mount points, set up manually by the user or admin.<\/p>\n
What lives here:<\/strong> Usually nothing by default. It’s a staging area where sysadmins mount external drives, network shares, or disk images temporarily.<\/p>\n
Think of it as:<\/strong> A temporary parking spot. You use it, then move on.<\/p>\n
Difference from \/media<\/code>:<\/strong> \/media<\/code> is for auto-mounted removable devices. \/mnt<\/code> is for manual, admin-controlled mounts.<\/p>\n
\/opt<\/code> \u2014 The Optional Extras<\/strong><\/h3>\n
What it is:<\/strong> Optional add-on software packages.<\/p>\n
What lives here:<\/strong> Third-party applications that don’t follow the standard Linux file layout \u2014 like Google Chrome, custom enterprise software, or manually installed tools.<\/p>\n
Think of it as:<\/strong> The “extras” shelf. Software installed here keeps all its files together in its own subdirectory, instead of scattering them across the system.<\/p>\n
Example:<\/strong> \/opt\/google\/chrome\/<\/code> \u2014 everything Chrome needs, neatly contained.<\/p>\n
\/proc<\/code> \u2014 The Live Dashboard<\/strong><\/h3>\n
What it is:<\/strong> A virtual filesystem that exposes real-time kernel and process information.<\/p>\n
What lives here:<\/strong> It’s not real files on disk \u2014 it’s the kernel pretending<\/em> files exist to give you live system info. \/proc\/cpuinfo<\/code> shows your CPU details. \/proc\/meminfo<\/code> shows RAM usage. \/proc\/1234\/<\/code> shows everything about the process with ID 1234.<\/p>\n
Think of it as:<\/strong> A live dashboard showing what the system is doing right now<\/em>.<\/p>\n
Cool trick:<\/strong> Run cat \/proc\/cpuinfo<\/code> and see your CPU specs printed straight from the kernel. No app needed.<\/p>\n
\/root<\/code> \u2014 The Admin’s Home<\/strong><\/h3>\n
What it is:<\/strong> The home directory of the root user<\/strong> (system administrator).<\/p>\n
What lives here:<\/strong> Personal files, scripts, and configs belonging to the superuser.<\/p>\n
Think of it as:<\/strong> The manager’s private office. Regular users don’t have access here.<\/p>\n
Why not \/home\/root<\/code>?<\/strong> Because if \/home<\/code> is on a separate partition and fails to mount, the root user still needs a home directory to log in and fix things. \/root<\/code> stays close to the base system.<\/p>\n
\/sbin<\/code> \u2014 Admin-Only Tools<\/strong><\/h3>\n
What it is:<\/strong> System binaries reserved for the superuser.<\/p>\n
What lives here:<\/strong> System administration commands like mount<\/code>, fsck<\/code> (filesystem check), iptables<\/code>, reboot<\/code>, and shutdown<\/code>.<\/p>\n
Think of it as:<\/strong> The staff-only section of the toolkit. Regular users can see these tools exist but can’t run most of them without sudo<\/code>.<\/p>\n
\/srv<\/code> \u2014 Service Data<\/strong><\/h3>\n
What it is:<\/strong> Data for services provided by the system.<\/p>\n
What lives here:<\/strong> If your Linux machine runs a web server, FTP server, or data repositories, the files they serve live here. For example, \/srv\/www\/<\/code> for website files or \/srv\/ftp\/<\/code> for FTP content.<\/p>\n
Think of it as:<\/strong> The stockroom behind a shop counter \u2014 where the goods being “served” are stored.<\/p>\n
Honestly?<\/strong> Many distros don’t use \/srv<\/code> consistently. You’ll mostly care about it when setting up servers.<\/p>\n
\/usr<\/code> \u2014 The Big Library<\/strong><\/h3>\n
What it is:<\/strong> User binaries and a secondary hierarchy of programs, libraries, and documentation.<\/p>\n
What lives here:<\/strong> Most of the software you install ends up here \u2014 \/usr\/bin\/<\/code> (user commands), \/usr\/lib\/<\/code> (libraries), \/usr\/share\/<\/code> (shared data), \/usr\/local\/<\/code> (locally compiled software).<\/p>\n
Think of it as:<\/strong> A massive library building that holds most of the system’s knowledge and tools.<\/p>\n
Fun fact:<\/strong> \/usr<\/code> used to stand for “Unix System Resources.” It’s often the largest directory on a Linux system.<\/p>\n
\/var<\/code> \u2014 The Living Log<\/strong><\/h3>\n
What it is:<\/strong> Variable data \u2014 files that change constantly as the system runs.<\/p>\n
What lives here:<\/strong> Log files (\/var\/log\/<\/code>), mail spools (\/var\/mail\/<\/code>), printer queues, databases, and cached package data (\/var\/cache\/<\/code>).<\/p>\n
Think of it as:<\/strong> The system’s diary \u2014 a continuous record of what’s happening, what’s been queued, and what’s waiting to be processed.<\/p>\n
Sysadmins love \/var\/log<\/code>:<\/strong> Almost every problem you ever debug on Linux has a clue hiding somewhere in \/var\/log<\/code>. It’s the first place to look when something breaks.<\/p>\n
Quick Reference Cheat Sheet<\/strong><\/h2>\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Directory<\/th>\nOne-Line Purpose<\/th>\n<\/tr>\n<\/thead>\n
\/<\/code><\/td>\nRoot \u2014 everything starts here<\/td>\n<\/tr>\n
\/bin<\/code><\/td>\nBasic commands (ls, cp, mv)<\/td>\n<\/tr>\n
\/boot<\/code><\/td>\nKernel and bootloader files<\/td>\n<\/tr>\n
\/dev<\/code><\/td>\nHardware as files<\/td>\n<\/tr>\n
\/etc<\/code><\/td>\nSystem configuration files<\/td>\n<\/tr>\n
\/home<\/code><\/td>\nPersonal user directories<\/td>\n<\/tr>\n
\/lib<\/code> \/lib64<\/code><\/td>\nShared libraries for core programs<\/td>\n<\/tr>\n
\/media<\/code><\/td>\nAuto-mounted removable drives<\/td>\n<\/tr>\n
\/mnt<\/code><\/td>\nManual temporary mount points<\/td>\n<\/tr>\n
\/opt<\/code><\/td>\nOptional third-party software<\/td>\n<\/tr>\n
\/proc<\/code><\/td>\nLive kernel and process info<\/td>\n<\/tr>\n
\/root<\/code><\/td>\nRoot user’s home directory<\/td>\n<\/tr>\n
\/sbin<\/code><\/td>\nAdmin-only system commands<\/td>\n<\/tr>\n
\/srv<\/code><\/td>\nData served by system services<\/td>\n<\/tr>\n
\/usr<\/code><\/td>\nUser programs, libs, and docs<\/td>\n<\/tr>\n
\/var<\/code><\/td>\nLogs, spools, and variable data<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
The Big Picture: Why This Design Is Genius<\/strong><\/h2>\n
Linux’s filesystem hierarchy isn’t arbitrary \u2014 it’s deliberately separated by purpose and permission level:<\/strong><\/p>\n
    \n
  • Stability vs. Change:<\/strong> Static system files (\/bin<\/code>, \/lib<\/code>) are kept separate from constantly-changing data (\/var<\/code>). This makes backups and system recovery far easier.<\/li>\n
  • User vs. Admin:<\/strong> Regular users live in \/home<\/code>. The system admin lives in \/root<\/code>. Admin tools live in \/sbin<\/code>. The separation is intentional and enforces security.<\/li>\n
  • Essential vs. Optional:<\/strong> Core stuff (\/bin<\/code>, \/etc<\/code>) is separate from optional extras (\/opt<\/code>). If a non-essential partition fails, the core system still runs.<\/li>\n<\/ul>\n
    This is why Linux powers 96% of the world’s top web servers, every Android phone, and most cloud infrastructure. The design is built to be reliable, recoverable, and scalable.<\/p>\n","protected":false},"excerpt":{"rendered":"
    You Opened a Linux Terminal. Now What? You typed ls \/ and got hit with a wall of folders \u2014 bin, boot, dev, etc, home, lib\u2026 and your brain said “nope.” Don’t worry. Every Linux user has been there. Here’s the truth: Linux’s filesystem isn’t random. It follows a beautiful, logical standard called the Filesystem […]<\/p>\n","protected":false},"author":24,"featured_media":6597,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[250],"tags":[],"class_list":["post-6579","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux"],"yoast_head":"\nLinux Filesystem Hierarchy Guide: Beginner to Expert<\/title>\n<meta name=\"description\" content=\"Learn Linux filesystem hierarchy from root to advanced. Understand directories, structure, and best practices with this complete beginner-to-expert guide.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Linux Filesystem Hierarchy Guide: Beginner to Expert\" \/>\n<meta property=\"og:description\" content=\"Learn Linux filesystem hierarchy from root to advanced. Understand directories, structure, and best practices with this complete beginner-to-expert guide.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/\" \/>\n<meta property=\"og:site_name\" content=\"GlobeSign\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/Globe-Sign-447604478609140\" \/>\n<meta property=\"article:published_time\" content=\"2026-04-29T12:35:01+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-29T21:19:29+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.globesign.com\/blog\/wp-content\/uploads\/2026\/04\/roman-synkevych-E-V6EMtGSUU-unsplash-scaled.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"2560\" \/>\n\t<meta property=\"og:image:height\" content=\"1707\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Muhammad Haris\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@Globesign1\" \/>\n<meta name=\"twitter:site\" content=\"@Globesign1\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Muhammad Haris\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\\\/\"},\"author\":{\"name\":\"Muhammad Haris\",\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/#\\\/schema\\\/person\\\/cda79d5096897b85472573c60ef2d6f8\"},\"headline\":\"Linux Filesystem Hierarchy Explained: The Complete Guide (Beginner to Expert)\",\"datePublished\":\"2026-04-29T12:35:01+00:00\",\"dateModified\":\"2026-04-29T21:19:29+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\\\/\"},\"wordCount\":1441,\"image\":{\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/roman-synkevych-E-V6EMtGSUU-unsplash-scaled.jpg\",\"articleSection\":[\"Linux\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\\\/\",\"url\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\\\/\",\"name\":\"Linux Filesystem Hierarchy Guide: Beginner to Expert\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/roman-synkevych-E-V6EMtGSUU-unsplash-scaled.jpg\",\"datePublished\":\"2026-04-29T12:35:01+00:00\",\"dateModified\":\"2026-04-29T21:19:29+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/#\\\/schema\\\/person\\\/cda79d5096897b85472573c60ef2d6f8\"},\"description\":\"Learn Linux filesystem hierarchy from root to advanced. Understand directories, structure, and best practices with this complete beginner-to-expert guide.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.globesign.com\\\/blog\\\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/roman-synkevych-E-V6EMtGSUU-unsplash-scaled.jpg\",\"contentUrl\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/roman-synkevych-E-V6EMtGSUU-unsplash-scaled.jpg\",\"width\":2560,\"height\":1707,\"caption\":\"Linux Filesystem Hierarchy Explained: The Complete Guide (Beginner to Expert)\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Linux Filesystem Hierarchy Explained: The Complete Guide (Beginner to Expert)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/\",\"name\":\"GlobeSign\",\"description\":\"Website Design and Development Company in Canada\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/#\\\/schema\\\/person\\\/cda79d5096897b85472573c60ef2d6f8\",\"name\":\"Muhammad Haris\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/cropped-Profile-Picture-1-96x96.png\",\"url\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/cropped-Profile-Picture-1-96x96.png\",\"contentUrl\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/cropped-Profile-Picture-1-96x96.png\",\"caption\":\"Muhammad Haris\"},\"description\":\"Muhammad Haris is a DevOps and Cloud Engineer with a strong foundation in software engineering, specializing in architecting and automating the full lifecycle of modern, data-intensive applications. From AI\\\/ML model experimentation to production-grade cloud deployment, He designs resilient infrastructures that transform innovation into scalable, reliable systems.\",\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/muhammad-haris-323268236\\\/\"],\"url\":\"https:\\\/\\\/www.globesign.com\\\/blog\\\/author\\\/harris\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Linux Filesystem Hierarchy Guide: Beginner to Expert","description":"Learn Linux filesystem hierarchy from root to advanced. Understand directories, structure, and best practices with this complete beginner-to-expert guide.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/","og_locale":"en_US","og_type":"article","og_title":"Linux Filesystem Hierarchy Guide: Beginner to Expert","og_description":"Learn Linux filesystem hierarchy from root to advanced. Understand directories, structure, and best practices with this complete beginner-to-expert guide.","og_url":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/","og_site_name":"GlobeSign","article_publisher":"https:\/\/www.facebook.com\/Globe-Sign-447604478609140","article_published_time":"2026-04-29T12:35:01+00:00","article_modified_time":"2026-04-29T21:19:29+00:00","og_image":[{"width":2560,"height":1707,"url":"https:\/\/www.globesign.com\/blog\/wp-content\/uploads\/2026\/04\/roman-synkevych-E-V6EMtGSUU-unsplash-scaled.jpg","type":"image\/jpeg"}],"author":"Muhammad Haris","twitter_card":"summary_large_image","twitter_creator":"@Globesign1","twitter_site":"@Globesign1","twitter_misc":{"Written by":"Muhammad Haris","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/#article","isPartOf":{"@id":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/"},"author":{"name":"Muhammad Haris","@id":"https:\/\/www.globesign.com\/blog\/#\/schema\/person\/cda79d5096897b85472573c60ef2d6f8"},"headline":"Linux Filesystem Hierarchy Explained: The Complete Guide (Beginner to Expert)","datePublished":"2026-04-29T12:35:01+00:00","dateModified":"2026-04-29T21:19:29+00:00","mainEntityOfPage":{"@id":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/"},"wordCount":1441,"image":{"@id":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/#primaryimage"},"thumbnailUrl":"https:\/\/www.globesign.com\/blog\/wp-content\/uploads\/2026\/04\/roman-synkevych-E-V6EMtGSUU-unsplash-scaled.jpg","articleSection":["Linux"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/","url":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/","name":"Linux Filesystem Hierarchy Guide: Beginner to Expert","isPartOf":{"@id":"https:\/\/www.globesign.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/#primaryimage"},"image":{"@id":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/#primaryimage"},"thumbnailUrl":"https:\/\/www.globesign.com\/blog\/wp-content\/uploads\/2026\/04\/roman-synkevych-E-V6EMtGSUU-unsplash-scaled.jpg","datePublished":"2026-04-29T12:35:01+00:00","dateModified":"2026-04-29T21:19:29+00:00","author":{"@id":"https:\/\/www.globesign.com\/blog\/#\/schema\/person\/cda79d5096897b85472573c60ef2d6f8"},"description":"Learn Linux filesystem hierarchy from root to advanced. Understand directories, structure, and best practices with this complete beginner-to-expert guide.","breadcrumb":{"@id":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/#primaryimage","url":"https:\/\/www.globesign.com\/blog\/wp-content\/uploads\/2026\/04\/roman-synkevych-E-V6EMtGSUU-unsplash-scaled.jpg","contentUrl":"https:\/\/www.globesign.com\/blog\/wp-content\/uploads\/2026\/04\/roman-synkevych-E-V6EMtGSUU-unsplash-scaled.jpg","width":2560,"height":1707,"caption":"Linux Filesystem Hierarchy Explained: The Complete Guide (Beginner to Expert)"},{"@type":"BreadcrumbList","@id":"https:\/\/www.globesign.com\/blog\/linux-filesystem-hierarchy-explained-the-complete-guide-beginner-to-expert\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.globesign.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Linux Filesystem Hierarchy Explained: The Complete Guide (Beginner to Expert)"}]},{"@type":"WebSite","@id":"https:\/\/www.globesign.com\/blog\/#website","url":"https:\/\/www.globesign.com\/blog\/","name":"GlobeSign","description":"Website Design and Development Company in Canada","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.globesign.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.globesign.com\/blog\/#\/schema\/person\/cda79d5096897b85472573c60ef2d6f8","name":"Muhammad Haris","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.globesign.com\/blog\/wp-content\/uploads\/2026\/04\/cropped-Profile-Picture-1-96x96.png","url":"https:\/\/www.globesign.com\/blog\/wp-content\/uploads\/2026\/04\/cropped-Profile-Picture-1-96x96.png","contentUrl":"https:\/\/www.globesign.com\/blog\/wp-content\/uploads\/2026\/04\/cropped-Profile-Picture-1-96x96.png","caption":"Muhammad Haris"},"description":"Muhammad Haris is a DevOps and Cloud Engineer with a strong foundation in software engineering, specializing in architecting and automating the full lifecycle of modern, data-intensive applications. From AI\/ML model experimentation to production-grade cloud deployment, He designs resilient infrastructures that transform innovation into scalable, reliable systems.","sameAs":["https:\/\/www.linkedin.com\/in\/muhammad-haris-323268236\/"],"url":"https:\/\/www.globesign.com\/blog\/author\/harris\/"}]}},"_links":{"self":[{"href":"https:\/\/www.globesign.com\/blog\/wp-json\/wp\/v2\/posts\/6579","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.globesign.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.globesign.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.globesign.com\/blog\/wp-json\/wp\/v2\/users\/24"}],"replies":[{"embeddable":true,"href":"https:\/\/www.globesign.com\/blog\/wp-json\/wp\/v2\/comments?post=6579"}],"version-history":[{"count":4,"href":"https:\/\/www.globesign.com\/blog\/wp-json\/wp\/v2\/posts\/6579\/revisions"}],"predecessor-version":[{"id":6598,"href":"https:\/\/www.globesign.com\/blog\/wp-json\/wp\/v2\/posts\/6579\/revisions\/6598"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.globesign.com\/blog\/wp-json\/wp\/v2\/media\/6597"}],"wp:attachment":[{"href":"https:\/\/www.globesign.com\/blog\/wp-json\/wp\/v2\/media?parent=6579"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.globesign.com\/blog\/wp-json\/wp\/v2\/categories?post=6579"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.globesign.com\/blog\/wp-json\/wp\/v2\/tags?post=6579"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}