To download support materials, please select your product from the list below. You will automatically be shown all downloads for that product, including extensions, brochures, sales presenters and technotes.

  • 1. Select your section, category and chosen product.
  • 2. Click on the Manual, brochure, sales presenter or technote of your choice.
  • 3. Take careful note of any applicable instructions, especially for extensions.
  • 4. Download the file to your hard drive.
Knowledge Base

Knowledge Base

Magento 2 Directory Structure

Date Created: 23 May 2016
Last Updated: 10 Jul 2020

After installing Magento 2, you will not have any custom modifications to your site. If you are coming from Magento 1, knowing where to start adding your modules and editing themes can be daunting.

First, consider the web root for Magento 2 (2.1 as of this writing)

Some of this is familiar. The app,lib, and var directories were all part of Magento 1.  New in Magento 2 are bin, dev, phpserver, pub, setup, update, and vendor.

app contains the design folder for themes and the configuration file env.php
bin contains the Magento 2 command line tool named magento ,
dev contains testing files for the Magento 2 Functional Testing Framework
lib like Magento 1, various libraries and packages are in here
phpserver contains Router.php
pub contains generated static files and your site media
setup several important packages are in here, such as the performance toolkit
update this is similar to the downloader from Magento 1 and contains upgrade files
var like Magento 1, contains raw cache files,logs, and reports
vendor the closest to app/etc/modules you will get in Magento 2

That is the web root, but we don’t need to be concerned with all of it to work with Magento 2. Many of the core directories should be left alone, and until you really dig into Magento 2 development, you probably won’t be using the testing tools.  Only a few are directly used in managing the front and backends for your store.

Where are the themes stored?

Themes are all in app/design/frontend/ then in a vendor subfolder, which can have multiple themes under it.  Themes are fully detailed at the M2 devdocs.  From those docs a typical theme will look like this: