Microsoft Azure Storage Explorer: baixar versions anteriors

March 2026 (Version 1.42.0, build 20260317.3)
Welcome to Storage Explorer version 1.42.0. This version adds some new features for sharing resources and addresses these issues.
SAS Direct Links
Storage Explorer now supports SAS-based direct links. A SAS-based direct link looks just like an ordinary SAS URL, except it has the storageexplorer: protocol. For example:
- Blob container: storageexplorer://acct.blob.core.windows.net/container?sig=...
- File share directory: storageexplorer://acct.file.core.windows.net/share/dir1?sig=...
- Blob: storageexplorer://acct.blob.core.windows.net/container/dir1/blob.txt?sig=...
When following a direct link, Storage Explorer can automatically attach at the container root, attach at the target item’s directory, download the target item, or download and open the item.
To create a SAS direct link, just take an ordinary SAS URL and change the protocol to storageexplorer:. Keep in mind that only container (sr=c) or share (sr=s) resource SAS URLs are supported, due to permission requirements. If you want the direct link to point to a directory, blob, or file within the container or share, just add the path to the item as part of the URL.
Here is a table summarizing the different types of SAS direct links and their supported operations in Storage Explorer.
──────────┬──────────────────┬─────────────────┬────────────────────┬─────────────┬───────────────┬────────┬───────────────
Service │Target Item (path)│SAS Resource (sr)│SAS Permissions (sp)│Attach (root)│Attach (target)│Download│Download & Open
──────────┼──────────────────┼─────────────────┼────────────────────┼─────────────┼───────────────┼────────┼───────────────
Blob/DFS │Container │c │l │✅ │❌ │❌ │❌
──────────┼──────────────────┼─────────────────┼────────────────────┼─────────────┼───────────────┼────────┼───────────────
Blob/DFS │Blob │c │rl │✅ │✅ │✅ │✅
──────────┼──────────────────┼─────────────────┼────────────────────┼─────────────┼───────────────┼────────┼───────────────
Blob/DFS │Directory │c │rl │❌ │✅ │✅ │✅
──────────┼──────────────────┼─────────────────┼────────────────────┼─────────────┼───────────────┼────────┼───────────────
Blob/DFS │Blob │b │N/A │❌ │❌ │❌ │❌
──────────┼──────────────────┼─────────────────┼────────────────────┼─────────────┼───────────────┼────────┼───────────────
File Share│Share │s │l │✅ │❌ │❌ │❌
──────────┼──────────────────┼─────────────────┼────────────────────┼─────────────┼───────────────┼────────┼───────────────
File Share│File │s │rl │❌ │❌ │✅ │✅
──────────┼──────────────────┼─────────────────┼────────────────────┼─────────────┼───────────────┼────────┼───────────────
File Share│File │f │N/A │❌ │❌ │❌ │❌
──────────┼──────────────────┼─────────────────┼────────────────────┼─────────────┼───────────────┼────────┼───────────────
Queue │Queue │N/A │r │✅ │❌ │❌ │❌
──────────┼──────────────────┼─────────────────┼────────────────────┼─────────────┼───────────────┼────────┼───────────────
Table │Table │N/A │r │✅ │❌ │❌ │❌
──────────┴──────────────────┴─────────────────┴────────────────────┴─────────────┴───────────────┴────────┴───────────────
HTTPS Connections with Azurite
Azurite supports HTTPS communications using self-signed certificates. Storage Explorer can now detect and automatically connect to Azurite containers configured to use HTTPS.
In order for Storage Explorer to communicate successfully, you need to add the self-signed certificate to your system's certificate store. You also need to import the certificate into Storage Explorer. You can do this from the Edit → SSL Certificates → Import Certificates menu.
New Feedback Experience
In this version, we've streamlined the experience to make it easier to report issues, open service requests, and provide feedback via our survey. The Feedback button in the vertical toolbar now opens a dialog with these options:
- Report issue - opens the Storage Explorer GitHub issues page.
- Get help - navigates to the Azure Portal's "Help + support" page.
- Help us improve - op

February 2026 (Version 1.41.1, build 20260214.2)
Welcome to Storage Explorer version 1.41.1. This version updates the bundled version of .NET to 8.0.24 and addresses these issues.
Version 1.41.1 includes all features, improvements, and bug fixes from 1.41.0, which completes support for NFS files and brings improvements to Azurite container support. For a detailed list of all issues closed in 1.41.0, visit our Issues page.

January 2026 (Version 1.41.0, build 20260130.7)
Welcome to Storage Explorer version 1.41.0. This version completes support for NFS files and brings improvements to Azurite container support.
For a detailed list of all issues closed, visit our Issues page.
NFS File Share Support
This version of Storage Explorer includes AzCopy 10.31, which enhances support for NFS file shares. In addition to features introduced in version 1.40.0, you can now:
- Transfer files and directories between NFS and SMB file shares.
- Preserve symlinks when transferring files (symlinks remain percent encoded when downloaded, see #8841).
- View POSIX properties for files and directories in the Properties dialog.
Azurite Instances in Docker and Podman Containers
Version 1.36.0 introduced support for automatically detecting and connecting to Azurite instances running in local Docker containers. Version 1.41.0 extends this support to include Podman containers.
Configuring Azurite Communication Channels
To add support for both Docker and Podman, Storage Explorer now detects Azurite containers differently. Instead of invoking the Docker or Podman CLI, Storage Explorer communicates directly with the Docker and Podman engines via their named pipes (Windows) or Unix domain sockets (Linux and macOS).
By default, Storage Explorer looks in the following locations for these communication channels:
────────┬──────────────────────────────
Platform│Locations
────────┼──────────────────────────────
Windows │\\.pipe\docker_engine
────────┼──────────────────────────────
│\\.pipe\podman-machine-default
────────┼──────────────────────────────
macOS │/var/run/docker.sock
────────┼──────────────────────────────
Linux │/var/run/docker.sock
────────┼──────────────────────────────
│~/.docker/run/docker.sock
────────┴──────────────────────────────
For custom setups, you can add or modify locations using the new Azurite Communication Channels setting (services.storageAccounts.containerSocketPaths).
Linux Snap Support
For Linux snap users, the Docker snap dependency has been removed. You no longer need to have the Docker snap installed for this feature to work.
The snap sandbox environment prevents Storage Explorer from accessing system files. You can work around this by opening a socket that forwards communications to the Docker or Podman engine using socat:
1. Verify the location of the container engine socket (for example, /var/run/docker.sock).
2. Create a forwarding socket within an accessible location, such as your home directory:
socat UNIX-LISTEN:$HOME/docker.sock,fork UNIX-CONNECT:/var/run/docker.sock &
3. Launch Storage Explorer.
4. Modify the Azurite Communication Channels setting to include the absolute path to the forwarding socket (in this case, /home/<username>/docker.sock).
5. Refresh the Emulators & Attached node.
Note:
- The forwarding socket must be opened in a location that Storage Explorer can access, such as your home directory.
- The forwarding socket must not be a hidden file (that is, its name can't start with a dot).
- You must enter an absolute path to the forwarding socket for the Azurite Communication Channels setting. You can't use expanding shell characters, such as "~".
- If you terminate the background process launched by socat, Storage Explorer won't be able to communicate with the container engines to find Azurite instances.
Improvements for Managing Custom Environments
If you sign in to a custom Azure environment, it's now easier to configure essential environment properties. In addition to the ARM management endpoint, you can also specify audience endpoints, the Microsoft Graph endpoint, and the Azure Service Management (ASM) endpoint. These values are optional and can be autofilled.
Electron 39
Storage Explorer now uses Electron 39. You can learn more from the Electron blog.
Known Issues
If you have installed the Linux snap for the first time, there is a known issue where Storage Explorer may not remember new attachments or proxy credential upd

October 2025 (Version 1.40.2, build 20251101.1)
Welcome to Storage Explorer version 1.40.2. This release updates the bundled version of .NET to 8.0.21 and fixes an issue users may have encountered when trying to sign in to Azure China or Azure US Government clouds.
Version 1.40.2 includes features and bug fixes from 1.40.0. For a detailed list of all issues closed, visit our Issues page.
Downloading from NFS File Shares
In Storage Explorer version 1.40.0, we introduced support for uploading and downloading files from NFS file shares on Linux systems. Some users may have encountered issues when downloading files from NFS file shares. The files are downloaded, but the operation appears to fail in Storage Explorer.
AzCopy will not download anything from an NFS file share unless the --preserve-permissions option is provided. This option instructs AzCopy to preserve the original file's ownership on the local machine. However, this requires running AzCopy with sudo, because AzCopy needs to change file ownership, which requires elevated privileges. Storage Explorer cannot invoke AzCopy with sudo. This leads to the issue where downloads appear to fail regardless of settings.
If you encounter this issue, you can work around it by copying the AzCopy command and executing it directly from the command line with sudo.
This issue will be addressed in a future version of Storage Explorer.
Electron 38
Storage Explorer now uses Electron 38. You can learn more from the Electron blog.

September 2025 (Version 1.40.0, build 20250925.27)
Welcome to Storage Explorer version 1.40.0. This release adds new features for file shares and tables. For a detailed list of all issues closed, visit our Issues page.
NFS File Shares
Storage Explorer now supports working with NFS file shares. If you have access to Premium File storage accounts, you can now manage NFS file shares in those accounts.
In this release, Storage Explorer supports the following operations:
- Create NFS file shares. Storage Explorer will ask you whether you want to create an SMB or an NFS file share after entering the name of the new file share.
- Copy and paste NFS file shares between storage accounts.
- Create, manage, and delete NFS file share snapshots.
- Copy and paste files and folders between NFS file shares. Transfers between NFS and SMB, SMB and NFS, NFS and blob, and blob and NFS will be available in a future release.
- Upload to or download from NFS file shares (Linux only; Windows and macOS support will come in a future release).
We've also updated the Transfers → Preserve Info and Transfers → Preserve Permissions settings to reflect the NFS changes. We recommend enabling these settings when uploading or downloading from NFS file shares. This will help prevent ownership issues when downloading files.
When downloading from NFS file shares, AzCopy will attempt to modify the ownership of the local file to match the ownership of the file in the NFS file share. Errors may occur if your Linux user is not the owner. You can work around ownership-related errors by copying the AzCopy command used by Storage Explorer and run it directly from the command line using sudo.
Azure support for NFS file shares is ongoing. We will continue to improve NFS support as more platform features become available.
JSON Support for Table Import/Export
Storage Explorer now supports the option of importing and exporting table data in JSON format. JSON is better suited for developer workflows than CSV.
JSON Format
The expected JSON format is similar to the payload format for table service operations:
[
{
"PartitionKey": "p1",
"RowKey": "r1",
"Value1": "1",
"Value1@type": "Int32",
"Value2": "1.4",
"Value2@type": "Edm.Double",
"Value3": "true",
"Value3@odata.type": "Boolean",
"Value4": "example",
"Value4@type": "Edm.String"
},
{
"PartitionKey": "p1",
"RowKey": "r2",
"Value1": "2",
"Value2": "1.5"
}
]
Type annotations are optional and can be expressed using the @type or @odata.type suffixes. Type values can include the Edm. prefix.
To prevent data loss, Storage Explorer expects all values to be represented as JSON strings. This helps prevent precision errors when parsing numbers, such as large Int64 values or certain Double values.
Storage Explorer can infer data types without type annotations, but there are situations where the type cannot be unambiguously determined. For example, "123" could be an Int32 or an Int64, and "Jane" could be a Binary or a String. For this reason, we recommend providing type annotations whenever possible.
Using Type Annotations as a Schema
Table imports have also been improved to better handle data that adheres to a schema.
Azure Tables are inherently schemaless—they don't ensure all entities in the table have the same set of properties with the same data types. However, users often model their data using schemas. In such cases, type annotations for all entities in import/export files become redundant.
In this version, we've added the option to export type annotations for the first entity only. This option helps preserve important type information while reducing the size of the exported file.
Storage Explorer can take advantage of files that only have type annotations for the first entity. When you select an import file, the Import dialog samples the first few entities to determine the best types for each property. If you disable the "Infer types for unannotated property values" option, Storage Explorer will select property types based on the t

July 2025 (Version 1.39.1, build 20250715.1, Windows x64 and Windows ARM64 build 20250719.5)
Welcome to Storage Explorer version 1.39.1. This release addresses several additional issues that were not resolved in 1.39.0.
Version 1.39.1 includes feature enhancements and bug fixes from 1.39.0. For a detailed list of all issues closed in 1.39.0, visit our Issues page.
AzCopy for Windows ARM
Storage Explorer for Windows ARM now comes with an ARM-native binary of AzCopy. Windows ARM users can now benefit from improved performance and reduced memory usage when transferring data with AzCopy.
Windows .NET Installation Improvements
To help users keep Storage Explorer components up to date, the Storage Explorer installer for Windows now compares the latest version of the .NET Runtime installed with the version of .NET that comes bundled with Storage Explorer. If the installed version is older than the bundled version, the Storage Explorer will prompt you to install the newer version.
Storage Explorer Snap Base Upgraded to core22
The Storage Explorer snap for Linux has been upgraded to use the core22 base snap. This change was introduced in 1.39.0. For most users, this change is seamless and requires no additional action.

February 2024 (Version 1.33.0, build 20240301.4)
Welcome to Storage Explorer version 1.33.0. A detailed list of all issues closed for this release can be found on our Issues page. For a look at major changes, continue reading below.Data Explorer Improvements
Several changes have been made to Storage Explorer's data explorers as part of continuing to improve user experiences.The customize columns dialog has been refreshed with enhanced usability in mind. Columns can be resized to exact values from within the dialog, checkboxes to show/hide columns were changed to buttons, and the overall look and feel of the dialog has been updated.As a reminder, as of 1.32.0, all data explorers now support customizing columns. Columns can be customized by any of the following methods:- Click & drag column borders to resize
- Click & drag headers to reorder
- Right-click any header and choose Customize Columns...
- The Customize Columns button in the toolbar (tables only)
For all data explorers, sorting a column which contains string values now uses natural sort instead of lexicographic sort. If you prefer to continue using lexicographic sorting, you can disable natural sort by going to Settings (gear on the left) → Data Explorers → Natural Sort Order, and unchecking the checkbox.Finally, two quality-of-life changes were made to the table data explorer specifically. First, you can now reset columns via a pop out menu next to the Customize Columns button in the toolbar. This functionality makes it possible to reset table columns to the default PartitionKey and RowKey columns when a table has no entities. Second, when deleting a table, the saved columns for the table will be cleared from saved column settings. This means that when you delete a table in a storage account, and then create a new one with the same name, none of the columns from the old version of the table will appear until you add entities which have those same columns.Import Queue Messages from File
You can now import messages into a queue from a .csv file. To begin importing messages use the Import button in the queue data explorer's toolbar. Queue message import currently supports .csv files with no headers, where each row is a message, and the value in the first column is the message text. Each message created during import will have the default time to live and visibility timeout. If you'd like to provide input on more advanced import queue message functionality, please open an issue on GitHub.Formatting Datetimes in Avro & Parquet Preview
For Avro and Parquet file preview, datetimes are no longer rendered as their raw value. Instead, they will now be rendered as UTC datetimes. The decision to use UTC datetimes instead of local datetimes was made following user feedback and discussion.Customize AzCopy Command Shell Language
When AzCopy is invoked from Storage Explorer, a Copy AzCopy Command to Clipboard action is often made available. This allows you to easily reuse, remix, or learn from a command which does the equivalent to the operation just performed. Previously, this command would be written in a shell language which was considered to be a good match for your current OS. Now you can tell Storage Explorer to use a specific shell language by going to Settings (gear on the left) → Transfers → AzCopy Command Shell Language and choosing a language. At this time, only PowerShell and Bash are supported. If you'd like to see other shell languages supported, please open an issue on GitHub.Splitting Nodes for ARM and Classic Storage Accounts
The nodes for ARM and classic storage accounts have been split to be under two separate group nodes. This has been done in anticipation of Azure's retirement of classic storage accounts on 8/31/2024. More information about this retirement can be found here. As a bonus, this split has allowed for the use of a more modern API when listing ARM storage accounts, which brings better performance when listing and interacting with ARM storage accounts.N

November 2023 (Version 1.32.1, build 20231114.10)
Welcome to Storage Explorer version 1.32.1. This release addresses several minor issues based on user feedback and fixes a few bugs. A full list of the closed issues in this release can be found here.

- Table explorer (saved per table)
- Blob explorer (saved across all blob containers)
- File explorer (saved across all file shares)
- Queue explorer (saved across all queues)
- Windows/Linux: Alt+Enter
- macOS: Command+I

- .flac (audio/flac)
- .mp3 (audio/mpeg)
- .oga (audio/ogg)
- .ogg (audio/ogg)
- .wav (audio/x-wav)