Skip to content

Material Files Open Source Manager With Native SMB and SFTP Support

Material Files Open Source Manager With Native SMB and SFTP Support

Material Files review: Fix Android 14 permission resets, set up Nextcloud WebDAV error-free, and weigh native cloud support against Solid Explorer privacy.

App summary

App
Material Files
Developer
Hai Zhang
License
GPL-3.0-or-later
Version
1.6.4
Size
Approximately 15 MB (varies by ABI and source)
Price
Free (Open Source)

Material Files WebDAV Setup: Connecting to Nextcloud Without Errors

Connecting Material Files to a self-hosted Nextcloud instance via WebDAV requires precise configuration because the app does not use proprietary APIs or automated discovery wizards. Users must navigate to the storage management screen, select “Add storage,” and choose the WebDAV protocol option rather than a generic cloud connector. The URL field demands the full endpoint path, typically ending in /remote.php/dav/files/username/, as omitting the trailing slash or user-specific directory often results in authentication failures or empty directory listings. Unlike commercial file managers that abstract these details behind OAuth flows, Material Files exposes the raw protocol parameters, placing the responsibility for correct path mapping entirely on the user.

Authentication handling in Material Files is strictly credential-based and lacks token refresh mechanisms common in closed-source alternatives. When connecting to Nextcloud, users should generate a dedicated app password within the Nextcloud security settings rather than using their primary account password. This practice enhances security and prevents connection drops caused by two-factor authentication challenges that Material Files cannot resolve interactively. The app stores these credentials locally in encrypted shared preferences, and network permissions are invoked only when the user actively initiates a browse or transfer operation, ensuring no background telemetry or keep-alive signals leak metadata to the server.

Troubleshooting WebDAV connections differs significantly from SMB or FTP due to HTTP-specific error codes and server-side configurations. If Material Files returns a 405 Method Not Allowed error, the issue usually stems from incorrect URL formatting or missing WebDAV modules on the server rather than credential problems. Connection timeouts on Android 14+ may indicate that the system is restricting background network activity, requiring users to disable battery optimization specifically for Material Files. Self-signed certificates on private Nextcloud instances will be rejected by default; users must explicitly trust the certificate fingerprint during the initial connection attempt, as the app refuses insecure connections silently to prevent man-in-the-middle attacks.

Scoped Storage on Android 14: Fixing Material Files Permission Resets

Android’s Scoped Storage enforcement fundamentally changed how file managers access external media, and Material Files complies through strict Storage Access Framework (SAF) integration. On devices running Android 11 through Android 14, direct path access to SD cards and USB OTG drives is blocked at the kernel level for non-system apps. Material Files requests SAF permissions per-volume, meaning users must grant access separately for each inserted SD card or connected USB drive through the system document picker. This is not a bug but a mandatory compliance mechanism; the app cannot bypass these restrictions without root access, and attempting to write to restricted paths without an active SAF grant will fail silently or produce permission denied errors.

Permission resets after system updates occur because Android invalidates previously granted URI permissions when the OS version increments or when the app is updated via certain channels. Users upgrading from Android 13 to Android 14 frequently find their SD card access revoked, requiring them to re-navigate to Storage settings and re-grant SAF permissions for each volume. This reset behavior is controlled by the Android platform, not Material Files, and affects all compliant file managers equally. To minimize disruption, users should verify SAF grants immediately after any system update before attempting bulk file operations, as partial permissions can lead to incomplete transfers or corrupted archive extractions.

Root access via libsu is entirely optional and unrelated to basic external storage management under Scoped Storage. Non-rooted users retain full read/write capabilities on SD cards and USB OTG drives through SAF, provided they complete the permission grant flow correctly. Root mode unlocks access to system partitions like /data and /system, but it does not improve SD card performance or bypass SAF requirements for portable storage. Confusion often arises because some legacy file managers used root to ignore Scoped Storage entirely; Material Files deliberately avoids this approach to maintain compatibility with unrooted devices and future Android versions where root exploits may be patched.

Material Files vs Solid Explorer: The Trade-Off Between Native Cloud and Privacy

Solid Explorer dominates the paid file manager market by offering native API integration with Google Drive, OneDrive, Dropbox, and Box, enabling seamless streaming and caching of cloud files. Material Files lacks these proprietary integrations entirely, forcing users to rely on standard protocols like WebDAV or SMB to access cloud-hosted content. This architectural difference means Solid Explorer users enjoy thumbnail previews, offline caching, and background sync for commercial clouds, while Material Files users must configure manual connections and accept slower directory listing times over HTTP-based protocols. The trade-off is intentional: avoiding proprietary SDKs eliminates tracking vectors and dependency on third-party API changes that could break functionality without notice.

The GPL-3.0-or-later license governing Material Files guarantees perpetual access to source code and prohibits tivoization or relicensing to proprietary terms. Solid Explorer remains closed-source with no public audit trail, requiring users to trust the developer’s privacy claims based solely on store descriptions. Material Files’ zero-tracking policy is verifiable through code inspection; network calls occur exclusively in response to explicit user actions, and no analytics libraries are bundled. For organizations or individuals operating under strict compliance regimes, this transparency outweighs the convenience of native cloud support, especially when sensitive data traverses self-hosted infrastructure where proprietary telemetry would constitute a policy violation.

Performance characteristics diverge sharply when accessing remote storage due to protocol overhead differences. Solid Explorer’s native Google Drive integration uses optimized REST endpoints with resumable uploads and delta sync, achieving near-native speeds for large transfers. Material Files accessing the same storage via WebDAV incurs HTTP request overhead for every directory listing and metadata query, resulting in noticeably slower browsing on high-latency connections. However, for SMBv3 shares on local networks, Material Files matches or exceeds Solid Explorer’s throughput because it uses native CIFS implementations without intermediate abstraction layers. Users prioritizing LAN performance and privacy over cloud convenience will find Material Files superior, while those dependent on commercial cloud ecosystems should acknowledge the friction of protocol-only access.

Who Should Skip Material Files: Missing Sync, Media Playback, and Cloud Backup

Material Files deliberately excludes automatic folder synchronization and background backup capabilities, making it unsuitable for users expecting set-and-forget cloud mirroring. There is no scheduled task engine, no photo upload queue, and no incremental backup logic; every transfer requires manual initiation and monitoring. Users seeking automated device-to-cloud or device-to-device synchronization should look elsewhere, as Material Files functions purely as an interactive browser and transfer tool. This limitation is architectural, not accidental; adding background services would require persistent permissions and network access that contradict the app’s privacy-first design philosophy.

The absence of integrated media playback and document viewing forces reliance on external applications for all content consumption. Tapping a video file launches the system default player or prompts an app chooser; there is no built-in codec library, playlist management, or subtitle rendering. Document previews for PDF, Office, or image formats similarly depend on installed third-party apps. Users accustomed to all-in-one file managers with embedded viewers will find this workflow fragmented and inefficient. Material Files assumes users have already curated their preferred media and document apps, positioning itself as a navigation layer rather than a content consumption platform.

Non-technical users uncomfortable with manual permission grants or protocol configuration will encounter significant friction during initial setup. The app does not provide guided wizards for SAF authorization, root access, or network storage mounting; each requires understanding Android permission models or server protocol specifics. Commercial competitors abstract these complexities behind onboarding flows and contextual help, whereas Material Files presents raw system dialogs and expects user competence. Those unwilling to troubleshoot permission resets after OS updates or configure WebDAV endpoints manually should consider simpler alternatives, as the learning curve is steep and documentation assumes baseline technical literacy.

Native Protocol Implementation and Network Architecture

Material Files implements SMB, SFTP, FTP, and WebDAV protocols natively without relying on external plugins or proprietary middleware. The SMB stack supports SMBv2 and SMBv3 with signing and encryption, enabling secure access to modern NAS devices and Windows shares without falling back to deprecated SMBv1. SFTP connections leverage OpenSSH-compatible key exchange algorithms and support both password and private key authentication, including ed25519 keys for enhanced security. FTP support includes explicit TLS encryption, though users should note that implicit FTPS is not supported due to widespread server incompatibility. All protocol handlers run in-process, eliminating IPC overhead and reducing attack surface compared to plugin-based architectures.

For users managing files across Tailscale or ZeroTier mesh networks, Material Files treats tunneled connections identically to LAN traffic because it operates at the application layer without network interface awareness. SMB shares exposed over Tailscale appear as standard IP addresses, and performance depends entirely on tunnel throughput rather than app-level optimization. This transparency enables seamless access to remote servers without VPN-specific configuration, though users must ensure DNS resolution works correctly within the mesh network. The app does not include built-in tunnel management; network connectivity must be established externally before launching Material Files.

Network permissions are scoped to user-initiated operations only, with no background services maintaining persistent connections. Browsing a remote directory triggers a discrete TCP session that closes upon navigation away or timeout; there is no connection pooling or keep-alive mechanism that could leak activity patterns. This design prevents battery drain and ensures network access is auditable through Android’s permission dashboard. Users concerned about metadata leakage can verify this behavior through packet capture tools, confirming that no traffic occurs outside explicit file operations. For lightweight direct NAS access without complex two-way sync configurations, FolderSync Fits Power Users Needing FTP And Tasker offers a complementary approach for automated workflows that Material Files intentionally omits.

Local Storage Management and Archive Handling

Local file operations in Material Files adhere strictly to Android storage APIs, with performance optimizations for high-latency removable media. Directory enumeration uses batched cursor queries to avoid UI thread blocking on folders containing thousands of files, a common pain point in naive file manager implementations. Copy and move operations leverage asynchronous I/O with progress callbacks, enabling cancellation and pause/resume functionality even for multi-gigabyte transfers. Checksum verification is available post-transfer for integrity validation, supporting MD5, SHA-1, and SHA-256 algorithms computed on-device without external dependencies.

Archive handling supports extraction and creation of ZIP, RAR, 7Z, and TAR formats through integrated libraries compiled from source. Extraction handles password-protected archives and preserves Unix permissions when unpacking to compatible filesystems. Creation supports configurable compression levels and split volumes for large archives, though solid compression is disabled by default to maintain extraction compatibility. Notably, the app does not support proprietary formats like ACE or LHA, reflecting its focus on open standards. Archive operations run in foreground services with notification progress indicators, preventing Android from killing long-running tasks during screen-off periods.

Text editing is handled through an integrated lightweight editor suitable for configuration files and scripts, with syntax highlighting for common programming languages. Changes save directly to the original file location when permissions allow, or prompt SAF overwrite confirmation for restricted paths. Binary files open in hex viewer mode for inspection without corruption risk. This built-in editor eliminates round-trips to external apps for quick edits, though users requiring advanced features like regex search or LSP integration should use dedicated editors. The editor respects monospace font preferences and line numbering settings configured in the app’s appearance menu.

Installation Channels and Update Mechanisms

Material Files distributes releases through both Google Play Store and F-Droid repositories, with identical functionality across channels. The Play Store version receives updates through standard Android delivery mechanisms, while F-Droid builds are compiled reproducibly from tagged source commits to ensure binary transparency. APK size varies by CPU architecture, ranging from approximately 8 MB for arm64-v8a to 15 MB for universal builds; users on metered connections should prefer architecture-specific downloads. Both distribution channels receive updates simultaneously, though F-Droid review cycles may introduce delays of 24-48 hours compared to Play Store availability.

As an open-source application frequently installed via alternative catalogs, Material Files benefits from F-Droid: An Open Source App Catalog for Android which verifies source code integrity and provides reproducible build metadata. F-Droid users receive update notifications through the catalog client rather than Play Services, enabling fully de-googled update workflows. Signature keys differ between Play Store and F-Droid distributions; switching channels requires uninstalling the existing version first to avoid signature mismatch errors. Users prioritizing supply chain security should prefer F-Droid builds, as they are built from verified source without proprietary Play Store DRM or licensing checks.

Version 1.6.4 represents the current stable release with fixes for Android 14 compatibility and SMBv3 negotiation edge cases. The changelog documents all changes transparently, including dependency updates and security patches. Backward compatibility extends to Android 5.0 (API 21), though older versions lack Scoped Storage workarounds and modern TLS cipher support. Users on legacy devices should expect reduced functionality despite successful installation. Development follows a conservative release cadence focused on stability over feature velocity, with beta builds available through GitHub Releases for early testing.

Privacy Model and Permission Transparency

Material Files requests only permissions strictly necessary for declared functionality, with no optional permissions for analytics or advertising. Storage permissions are limited to READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE on pre-API 30 devices, transitioning to granular media permissions on newer Android versions. Network permissions (INTERNET, ACCESS_NETWORK_STATE) enable protocol support but are never used for telemetry or ad delivery. Camera permission is requested only when scanning QR codes for Wi-Fi or server configuration import, and is revocable without impacting core functionality. No microphone, contacts, SMS, or location permissions are requested under any circumstance.

The app’s privacy posture aligns with broader open-source utility ecosystems that prioritize user agency over engagement metrics. Within the Simple Mobile Tools Fork: F-Droid Suite for Privacy Fans, Material Files occupies a niche for users needing advanced protocol support beyond basic file browsing while maintaining equivalent privacy guarantees. Unlike ad-supported free file managers that monetize through tracking, Material Files sustains development through voluntary donations and community contributions. This funding model eliminates incentives to expand permission scope or introduce dark patterns, as revenue is decoupled from user data extraction.

Users managing local files with Material Files often pair it with peer-to-peer synchronization tools to create comprehensive privacy-respecting workflows. While Material Files handles interactive browsing and manual transfers, Syncthing: A Full Review for Android provides automated device syncing without cloud intermediaries, distinguishing between direct file management and continuous replication. This separation of concerns prevents feature bloat and maintains each tool’s security boundaries. Combined, they enable end-to-end encrypted file workflows where no single component has access to both storage and sync credentials, reducing blast radius in case of compromise.

Pricing & Plans

  • Free: $0 forever. Includes full functionality across all supported protocols (SMB, SFTP, FTP, WebDAV), root access, archive handling, and text editing. No ads, no tracking, no premium tiers.
  • Donation: Voluntary contributions accepted via GitHub Sponsors, PayPal, or cryptocurrency. Donations do not unlock features or remove limitations; they sustain development time and infrastructure costs. Typical contributions range from $5-$20 annually.
  • Enterprise: No enterprise licensing or volume pricing exists. Organizations deploy the same GPL-3.0 build as individual users, with compliance obligations satisfied through source code availability rather than commercial contracts.

Who Should Use Material Files

  • System administrators managing Linux servers via SFTP who need native key-based authentication without proprietary cloud dependencies
  • Home lab enthusiasts accessing TrueNAS or Unraid shares over SMBv3 with encryption enabled
  • Privacy-conscious users replacing ad-supported file managers with auditable, tracker-free alternatives
  • Developers editing configuration files directly on Android devices with integrated syntax-highlighted editor
  • Nextcloud self-hosters requiring WebDAV access without installing official client apps

Comparison with Alternatives

FeatureMaterial FilesSolid ExplorerMiXplorer
LicenseGPL-3.0-or-laterProprietaryFreeware (closed)
PriceFree$2.99 one-timeFree / $4.99 Silver
Native Cloud APIsNoYes (Drive, OneDrive, Dropbox)Yes (extensive)
SMB/SFTP/WebDAVNative built-inPlugin requiredBuilt-in + plugins
Root Accesslibsu (optional)SupportedSupported
Integrated Media PlayerNoYesYes
Auto-Sync/BackupNoLimitedExtensive
Min Android Version5.0 (API 21)6.0 (API 23)5.0 (API 21)

Verdict

Material Files serves technical users who prioritize protocol fidelity, privacy transparency, and local/self-hosted storage management over commercial cloud convenience. Its native SMB, SFTP, FTP, and WebDAV implementations eliminate plugin dependencies and tracking vectors present in mainstream alternatives, making it ideal for system administrators, homelab operators, and privacy advocates. The deliberate exclusion of proprietary cloud APIs, media playback, and automated sync reflects a coherent design philosophy rather than missing features, but this coherence comes at the cost of mainstream accessibility.

Users requiring Google Drive integration, automatic photo backup, or embedded media players should choose Solid Explorer or MiXplorer instead. Non-technical users uncomfortable with SAF permission grants or manual protocol configuration will find the learning curve prohibitive. Material Files excels precisely where commercial file managers compromise: in environments where auditability matters more than convenience, and where self-hosted infrastructure replaces proprietary cloud services. For that specific audience, it remains the most trustworthy and capable open-source file manager available on Android.

Pros

  • Fully open-source with no ads or proprietary tracking
  • Comprehensive protocol support for remote servers without external dependencies
  • Active maintenance with regular updates addressing Android API changes

Cons

  • Lacks built-in cloud storage integration (e.g., Google Drive, Dropbox) compared to commercial alternatives
  • Advanced features like root access require manual permission granting which may confuse non-technical users
  • No integrated media player or document viewer; relies entirely on external apps
Download from the official source

The link goes straight to Hai Zhang. We do not host app files.

Open official page →

Frequently asked questions

Is Material Files free?

The recorded pricing model is Free (Open Source).

What license does it use?

It is listed under GPL-3.0-or-later.

Where can I download the official version?

The official link points to https://github.com/zhanghai/MaterialFiles.

This article was drafted with AI assistance using official developer documentation, release notes, privacy policies, and public data, then reviewed by an editor. We do not claim lab testing. The full method is on our Review Method page.