Static files in ASP.NET Core
Learn how to serve and secure static files and configure static file hosting middleware behaviors in an ASP.NET Core web app.
Static files in ASP.NET Core
View or download sample code (how to download)
Serve static files
Static files are stored within your project's web root directory. The default directory is <content_root>/wwwroot, but it can be changed via the UseWebRoot method. See Content root and Web root for more information.
The app's web host must be made aware of the content root directory.
::: moniker range=">= aspnetcore-2.0"
WebHost.CreateDefaultBuilder method sets the content root to the current directory:
::: moniker range="< aspnetcore-2.0"
Set the content root to the current directory by invoking UseContentRoot inside of
Static files are accessible via a path relative to the web root. For example, the Web Application project template contains several folders within the wwwroot folder:
The URI format to access a file in the images subfolder is http://<server_address>/images/<image_file_name>. For example, http://localhost:9189/images/banner3.svg.
::: moniker range=">= aspnetcore-2.1"
If targeting .NET Framework, add the Microsoft.AspNetCore.StaticFiles package to your project. If targeting .NET Core, the Microsoft.AspNetCore.App metapackage includes this package.
::: moniker range="= aspnetcore-2.0"
If targeting .NET Framework, add the Microsoft.AspNetCore.StaticFiles package to your project. If targeting .NET Core, the Microsoft.AspNetCore.All metapackage includes this package.
::: moniker range="< aspnetcore-2.0"
Add the Microsoft.AspNetCore.StaticFiles package to your project.
Configure the middleware which enables the serving of static files.
Serve files inside of web root
Invoke the UseStaticFiles method within
UseStaticFiles method overload marks the files in web root as servable. The following markup references wwwroot/images/banner1.svg:
In the preceding code, the tilde character
~/ points to webroot. For more information, see Web root.
Serve files outside of web root
Consider a directory hierarchy in which the static files to be served reside outside of the web root:
A request can access the banner1.svg file by configuring the Static File Middleware as follows:
In the preceding code, the MyStaticFiles directory hierarchy is exposed publicly via the StaticFiles URI segment. A request to http://<server_address>/StaticFiles/images/banner1.svg serves the banner1.svg file.
The following markup references MyStaticFiles/images/banner1.svg:
Set HTTP response headers
A StaticFileOptions object can be used to set HTTP response headers. In addition to configuring static file serving from the web root, the following code sets the
The files have been made publicly cacheable for 10 minutes (600 seconds) in the Development environment:
Static file authorization
The Static File Middleware doesn't provide authorization checks. Any files served by it, including those under wwwroot, are publicly accessible. To serve files based on authorization:
Store them outside of wwwroot and any directory accessible to the Static File Middleware.
Serve them via an action method to which authorization is applied. Return a FileResult object:
Enable directory browsing
Directory browsing allows users of your web app to see a directory listing and files within a specified directory. Directory browsing is disabled by default for security reasons (see Considerations). Enable directory browsing by invoking the UseDirectoryBrowser method in
Add required services by invoking the AddDirectoryBrowser method from
The preceding code allows directory browsing of the wwwroot/images folder using the URL http://<server_address>/MyImages, with links to each file and folder:
See Considerations on the security risks when enabling browsing.
Note the two
UseStaticFiles calls in the following example. The first call enables the serving of static files in the wwwroot folder. The second call enables directory browsing of the wwwroot/images folder using the URL http://<server_address>/MyImages:
Serve a default document
Setting a default home page provides visitors a logical starting point when visiting your site. To serve a default page without the user fully qualifying the URI, call the UseDefaultFiles method from
UseDefaultFilesmust be called before
UseStaticFilesto serve the default file.
UseDefaultFilesis a URL rewriter that doesn't actually serve the file. Enable Static File Middleware via
UseStaticFilesto serve the file.
UseDefaultFiles, requests to a folder search for:
The first file found from the list is served as though the request were the fully qualified URI. The browser URL continues to reflect the URI requested.
The following code changes the default file name to mydefault.html:
UseFileServer combines the functionality of
The following code enables the serving of static files and the default file. Directory browsing isn't enabled.
The following code builds upon the parameterless overload by enabling directory browsing:
Consider the following directory hierarchy:
The following code enables static files, default files, and directory browsing of
AddDirectoryBrowser must be called when the
EnableDirectoryBrowsing property value is
Using the file hierarchy and preceding code, URLs resolve as follows:
If no default-named file exists in the MyStaticFiles directory, http://<server_address>/StaticFiles returns the directory listing with clickable links:
UseDirectoryBrowseruse the URL http://<server_address>/StaticFiles without the trailing slash to trigger a client-side redirect to http://<server_address>/StaticFiles/. Notice the addition of the trailing slash. Relative URLs within the documents are deemed invalid without a trailing slash.
The FileExtensionContentTypeProvider class contains a
Mappings property serving as a mapping of file extensions to MIME content types. In the following sample, several file extensions are registered to known MIME types. The .rtf extension is replaced, and .mp4 is removed.
See MIME content types.
Non-standard content types
Static File Middleware understands almost 400 known file content types. If the user requests a file with an unknown file type, Static File Middleware passes the request to the next middleware in the pipeline. If no middleware handles the request, a 404 Not Found response is returned. If directory browsing is enabled, a link to the file is displayed in a directory listing.
The following code enables serving unknown types and renders the unknown file as an image:
With the preceding code, a request for a file with an unknown content type is returned as an image.
[!WARNING] Enabling ServeUnknownFileTypes is a security risk. It's disabled by default, and its use is discouraged. FileExtensionContentTypeProvider provides a safer alternative to serving files with non-standard extensions.
UseStaticFilescan leak secrets. Disabling directory browsing in production is highly recommended. Carefully review which directories are enabled via
UseDirectoryBrowser. The entire directory and its sub-directories become publicly accessible. Store files suitable for serving to the public in a dedicated directory, such as <content_root>/wwwroot. Separate these files from MVC views, Razor Pages (2.x only), configuration files, etc.
The URLs for content exposed with
UseStaticFilesare subject to the case sensitivity and character restrictions of the underlying file system. For example, Windows is case insensitive—macOS and Linux aren't.
ASP.NET Core apps hosted in IIS use the ASP.NET Core Module to forward all requests to the app, including static file requests. The IIS static file handler isn't used. It has no chance to handle requests before they're handled by the module.
Complete the following steps in IIS Manager to remove the IIS static file handler at the server or website level:
- Navigate to the Modules feature.
- Select StaticFileModule in the list.
- Click Remove in the Actions sidebar.
[!WARNING] If the IIS static file handler is enabled and the ASP.NET Core Module is configured incorrectly, static files are served. This happens, for example, if the web.config file isn't deployed.
- Place code files (including .cs and .cshtml) outside of the app project's web root. A logical separation is therefore created between the app's client-side content and server-based code. This prevents server-side code from being leaked.
- Introduction to ASP.NET Core