vfs.toml file configures virtual filesystem (VFS) services that enable Yazi to access remote files and special file systems.
File Location
- Unix-like systems:
~/.config/yazi/vfs.toml - Windows:
%AppData%\yazi\config\vfs.toml
What is VFS?
Yazi’s Virtual File System (VFS) allows you to:- Access remote files via HTTP/HTTPS
- Browse cloud storage
- Work with virtual/network file systems
- Handle files that need special fetching logic
Configuration Structure
The VFS configuration consists of service definitions:Default Configuration
The defaultvfs-default.toml is minimal:
Service Types
VFS services can be configured for different protocols and use cases.HTTP/HTTPS Service
Access files over HTTP/HTTPS:string
default:"Http"
Service type identifier
string
Base URL for HTTP requests
table
Optional HTTP headers to include in requests
Custom Service
Define custom VFS services for specialized needs:string
default:"Custom"
Service type identifier
string
Command to fetch files. Use
%s as placeholder for the file URL.Service Usage in File Opening
VFS services work with the opener and file opening rules. When a file with a VFS MIME type is opened, Yazi can use the configured service to fetch it.VFS MIME Types
Yazi uses special MIME types for VFS files:vfs/absent- File is not yet fetchedvfs/stale- Cached file is outdated
yazi.toml:
Complete Example
Using VFS Services
Opening Remote Files
To open a remote file through VFS:- Configure the VFS service in
vfs.toml - Configure opener rules for VFS MIME types in
yazi.toml - Navigate to a VFS URL in Yazi
- Open the file - Yazi will fetch it using the configured service
URL Format
VFS URLs typically follow this format:Advanced Configuration
Caching
Fetched VFS files are cached in Yazi’s cache directory. The cache location is configured inyazi.toml:
Authentication
For services requiring authentication, use headers:Timeout Configuration
Configure request timeouts for HTTP services:Troubleshooting
Service Not Found
If you get “No such VFS service” error:- Check that the service is defined in
vfs.toml - Verify the service name matches the VFS URL
- Ensure
vfs.tomlhas no syntax errors
Fetch Failures
If files fail to fetch:- Check network connectivity
- Verify the base URL is correct
- Check authentication headers if required
- Look at Yazi’s error messages for details
Cache Issues
If cached files are stale:- Clear Yazi’s cache directory
- Restart Yazi to reload VFS configuration
- Check the file’s MIME type (should be
vfs/stalefor outdated cache)
Limitations
- VFS is primarily designed for read-only access
- Write operations to VFS files may not be supported
- Performance depends on network speed and service latency
- Some file operations may not work with VFS files