---
id: "en/mapped-drive"
title: "Mapped Drive"
language: "en"
description: "Introducing the ability of mapped disks to access cloud files like local disks, and the differences with WebDAV/SMB."
canonical_url: "https://www.babel.cc/public/babelwiki/en/mapped-drive.html"
markdown_url: "https://www.babel.cc/public/babelwiki/ai/en/mapped-drive.md"
alternates: {"en": "https://www.babel.cc/public/babelwiki/ai/en/mapped-drive.md", "zh": "https://www.babel.cc/public/babelwiki/ai/zh/mapped-drive.md"}
reading_note: "文档记录不等于当前部署能力；以实际版本、授权模块与配置为准。保留原文的可选、限制及待确认说明，勿补猜接口。 / Documentation is not a guarantee for every deployment. Preserve optional-module requirements, limitations and unresolved API contracts."
---

# Mapped Drive

The virtual mapped disk allows users to access BabelBird cloud files in Windows Explorer or macOS Finder as if they were a local disk. It is suitable for scenarios where the directory level is deep, the number of files is large, and users are accustomed to opening files with local file managers and professional software.

![Windows mapped drive](https://www.babel.cc/public/babelwiki/assets/images/mapped-drive-windows.jpg)
*The Windows client presents BabelBird mapped drive in File Explorer and keeps access within user permissions.*

![macOS mapped drive](https://www.babel.cc/public/babelwiki/assets/images/mapped-drive-mac.webp)
*The macOS client exposes the mapped drive in Finder for users who prefer native file management workflows.*

## Core Competencies

| Capabilities | Description | Support Platforms |
| --- | --- | --- |
| Explorer/Finder access | Access the network disk directory in the system file manager | Windows client, Mac client |
| Virtual drive letter/virtual path | Cloud files can be entered through drive letter or virtual path | Windows client, Mac client |
| Cache management | On-demand downloading and caching of files to reduce local disk usage | Windows client, Mac client |
| Editing automatically locks | Automatically locks when opening a file for editing in the mapped disk to reduce multi-person editing conflicts | Windows client, Mac client |
| File references and associated resources | Click a file to open file references and associated resources | Windows client, Mac client |
| Third-party program access | Local applications can access mapped disk files just like local paths | Windows client, Mac client |

## How to work

Windows mapped drives use CFAPI, the same platform mechanism used by OneDrive, to present cloud placeholders in File Explorer. Mac mapped drives use the native macOS File Provider framework. Placeholders can retain metadata while file content is downloaded on demand when read. Downloaded or edited content uses local storage, and even metadata-only items occupy a small amount of space. Ordinary folder synchronization maintains local file copies in selected directories; a sync folder must not be treated as disposable mapped-drive cache.

## Permissions and Network

- The range of files that users can see and operate is still determined by the Babel permission system.
- Access to the mapped disk relies on network connection; when the network is unavailable or permissions expire, uncached files cannot be opened normally.
- File editing, uploading new versions, deleting, moving, sharing, etc. should still be controlled by folder permissions, project permissions, and security policies.
- Linux clients, including Kylin, have the same synchronization capabilities as Windows and macOS and support editing files with local applications. Linux does not support mapped drives. Linux builds have the same capabilities; select the build for the distribution and processor architecture.

## Differences from WebDAV/SMB

| Dimensions | Virtual mapping disk | WebDAV/SMB |
| --- | --- | --- |
| Permission consistency | Consistent with Babel account, department, project, sharing and file access control | Often requires separate gateway or protocol permission mapping |
| Product integration | Can be combined with versions, locks, logs, associated resources, and client editing | Prefer common file protocols |
| Experience goals | Localized access experience for BabelBird cloud files | Access to network file systems |
| Applicable boundary | Depends on client and enterprise configuration | Depends on protocol service and network environment |

## Applicable suggestions

- When browsing a large amount of cloud data but do not want to download all cloud files in advance, use the mapped disk first.
- When you need to process fixed directories offline, use synchronized folders first.
- When using CAD, design, video, engineering and office professional software, you can maintain local opening habits through mapping disks.
- For sensitive directories, file access permissions, download control, watermarks and log auditing should be combined.

## Detailed description of the white paper

### Overview

- Virtual mapped disk: BabelBird Enterprise Drive introduces the virtual mapped disk function, which provides a way to seamlessly connect cloud files. You can access the mapped disk in Windows Explorer or Mac Finder just like accessing a local disk, thereby achieving an easy access to cloud files.

- Technical implementation: Windows mapped drives use CFAPI, while Mac mapped drives use macOS File Provider. Both present cloud directories and on-demand content through the system file manager, with local content managed according to the respective platform mechanisms.

### Main features

- Local access to cloud files: The virtual mapped disk allows users to access files and folders in their Babel Enterprise network disk through tools such as local file explorer or Finder.

- Local space used on demand: Mapped drives do not download all cloud content in advance, but metadata, opening, editing and caching still use local storage. The Windows cache location can be customized during first installation. Mac local content is managed by File Provider; the Windows installation option does not imply that Mac system caches can be relocated arbitrarily. Confirm successful upload and close editing applications before release; see the procedure at the end of this page.

- Online access: Content that has not downloaded requires network access. Downloaded content remains subject to account permissions and platform state. After local content is released, reading it again triggers on-demand downloading; a placeholder icon is not a complete offline copy.
- Transparent operation: Users can operate files in the virtual mapped disk just like local files, including opening, copying, pasting, deleting and other operations.

- Automatic synchronization: File changes will be automatically synchronized to the cloud, thereby maintaining the consistency of the cloud files and the files in the virtual mapped disk.

- Associated files: When you open a file with an associated file in the Babel mapping disk, the associated file will be automatically loaded, achieving the same effect as opening a file in a local folder. For example: opening a DWG (AutoCAD file) containing a large number of reference files, or an Excel chart associated with other files.

### Technical advantages (comparing WebDAV and SMB)

Mapped drives integrate with BabelBird accounts, departments, projects and file permissions, and can work with versions, locks and client editing. WebDAV and SMB permissions, encryption and performance depend on the server, client, protocol version and configuration. A protocol name alone does not establish a lack of enterprise permissions or encryption, nor support a performance comparison without test conditions.

Directory and file response times depend on file counts, network conditions, server load and local devices. This page does not promise lag-free operation or a fixed file-count performance threshold. Evaluate with real enterprise directories and concurrency before selecting a solution.

### Application scenarios

Virtual mapped disks are suitable for users who need to frequently access cloud files but do not want to change their local disk usage habits or download all cloud files in advance. This function allows users to access cloud files just like local files, and access network disks in other applications just like opening local folders, without changing usage habits, and facilitates file management and use.

## Cache location and releasing local content

| Platform | Confirmed implementation and location rule | Release boundary |
| --- | --- | --- |
| Windows | Uses CFAPI; the cache location can be customized during first installation | Release local content from the context menu of files or folders in the mapped drive, using the same workflow as OneDrive; availability depends on sync state and client policies |
| macOS | Uses native File Provider; the system manages downloaded content and dataless placeholders | Release local content from the context menu of files or folders in the mapped drive; do not delete internal system cache directories |

Platform documentation explains that CFAPI loads placeholder content on demand, with release controlled by sync state and provider policy; automatic release is optional. File Provider distinguishes materialized files from metadata-only dataless items and does not evict content with pending changes to synchronize. This is not a reason to ignore upload errors. See [Microsoft placeholder files](https://learn.microsoft.com/en-us/windows/win32/cfApi/build-a-cloud-file-sync-engine), [CFAPI sync policies](https://learn.microsoft.com/en-us/windows/win32/api/cfapi/ns-cfapi-cf_sync_policies), [Apple File Provider synchronization](https://developer.apple.com/documentation/fileprovider/synchronizing-the-file-provider-extension) and [Dataless file access](https://developer.apple.com/documentation/technotes/tn3150-getting-ready-for-data-less-files). These explain platform mechanisms, not exact menu wording in a BabelBird version.

Safe release procedure:

1. Confirm that the path belongs to a mapped drive, not an ordinary sync folder. Save edits, wait for successful upload, then close applications editing the file.
2. If uploads, conflicts or errors remain, first save readable originals and edits outside mapped drives and sync folders. Stop the release operation and ask an administrator to troubleshoot. A placeholder is not a complete backup of its content.
3. Open the mapped drive in File Explorer or Finder, right-click the relevant file or folder, and select the command to release local content. This retains the cloud file while removing downloaded content, using the same workflow as OneDrive. Do not choose Delete or manually delete cache directories.
4. Afterward, verify that the cloud file remains and its version and content are correct. While online and authorized, open it again to confirm it can download. Opening it uses local space again. If it fails, preserve the error details and independent copies for investigation.

Releasing local content is different from deleting a cloud file. Deleting from an ordinary sync folder can propagate to the cloud; mapped-drive cache cleanup instructions must not be applied to sync-folder contents. See [Troubleshooting FAQ](https://www.babel.cc/public/babelwiki/en/faq-technical.html).