Ray Fan edited this page Oct 3, 2018 · 2 revisions

Your uploaded images are resized and then saved in one of two places either on the file system or Azure Blob Storage.

If you want to have as few external services as possible or one day zip up your website and have all images that come with it, use the file system. But if you want these images off to a separate domain, I recommend Azure Blob Storage.

The choice can be configured in the appsettings.json

 "AppSettings": { 
   // Media file storage, "FileSystem" or "AzureBlob" 
   // "FileSystem": the files uploaded will be stored on the file system 
   // "AzureBlob": the files uploaded will be stored in Azure Blob Storage 
   "MediaStorageType": "FileSystem", 
   // File upload folder 
   // For FileSystem, it's a folder created in wwwroot 
   // For AzureBlob, it's a container created in your Azure storage account 
   "MediaContainerName": "media" 
 "ConnectionStrings": {
    // Azure Blob Storage connection string
    // When in dev, I recommend using Azure Storage Emulator
    // It's installed as part of the Azure SDK, windows > search "azure storage emulator" to start it,
    // When deploy to Azure, create this key with real connection string in your App Service > App settings > Connection strings
    // section, as this value will be overriden by that one.
    // Tip: you can use Azure Storage Explorer to manage local or remote azure storages
    "BlobStorageConnectionString": "UseDevelopmentStorage=true"

One tool you need to experiment Blob Storage is to download the Storage Emulator and Explorer, see the link above.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.