A standalone MudBlazor-based file explorer component with a compact list UI. Upload, copy, move, delete, etc.
src/MuddyFileExplorer- reusable Razor class librarysamples/MuddyFileExplorer.Sample- Blazor Web App sample using a sandboxed local file provider
- Dense MudBlazor file list using
MudDataGrid - Columns for icon, file name, size, type, and modified date
- Breadcrumb folder navigation
- Search/filter box
- New-file and new-folder actions
- Upload button and drag-and-drop upload area
- Queued uploads with per-file progress
- Provider-driven download action (files and folders)
- Context actions for open, rename, move, delete, and download
- Status bar for selected item/folder summary
Register MudBlazor in the host app:
builder.Services.AddMudServices();Include MudBlazor providers in the host layout:
<MudThemeProvider />
<MudPopoverProvider />
<MudDialogProvider />
<MudSnackbarProvider />Use the component with an IFileExplorerProvider implementation:
@using MuddyFileExplorer
@using MuddyFileExplorer.Components
<MuddyFileExplorer Provider="@FileProvider"
Dense="true"
MultiSelection="true"
MaxUploadFileSize="104857600" />Hosts implement IFileExplorerProvider for file operations:
- list folder contents
- list move targets
- create file
- create folder
- rename item
- move item
- delete item
- download item (file stream or folder zip stream)
- upload file with progress
The UI-facing models use opaque item IDs. Providers should not expose physical paths to the browser.
See styling.md for supported CSS hooks and examples for row density, font size, cell padding, and folder link/icon sizing.
Run the sample from this folder:
dotnet run --project samples/MuddyFileExplorer.Sample/MuddyFileExplorer.Sample.csprojThe sample stores demo files under samples/MuddyFileExplorer.Sample/App_Data/FileExplorerSandbox. It normalizes file paths, rejects traversal outside the sandbox, and serves downloads through the provider download API.