export const meta = { title: "Aspect + macOS Finder", description: "Learn how Aspect mounts appear in macOS Finder, how to pin them, configure cache, use open in mount, and switch between Finder file work and Aspect asset context.", tldr: "Mounting Aspect on macOS puts a project or folder in Finder like a shared drive, so editors can import, relink, Quick Look, and browse files while Aspect streams and caches data on demand. Pin the mount in the Finder sidebar, configure cache location and size for each workstation, and use offline pinning when files must be available without a connection. Open in mount jumps from an asset in Aspect to its file in Finder, while the Finder extension lets users pin for offline use or open a mounted file back in Aspect for review, metadata, approvals, and version context.", slug: "aspect-macos-finder", publishedAt: "2026-08-22", readingTime: 8, thumbnail: "https://cdn.aspectlabs.dev/blog/aspect-macos-finder/cover-e154cf87b903.png", authors: ["bright"], primaryTopic: "aspect-workflows", topics: ["aspect-workflows"], tags: ["aspect-integrations"], faq: [ { "question": "What does a mounted Aspect project look like in macOS Finder?", "answer": "A mounted Aspect project appears like a normal drive or shared file location in Finder. Users see folders and files in familiar Finder views, and they can use common macOS actions such as Quick Look, drag and drop, right-click menus, open dialogs, and path-based relinking in editing tools." }, { "question": "Does adding the Aspect mount to the Finder sidebar make it available offline?", "answer": "No. Adding the mount to the Finder sidebar creates a shortcut for faster access, but it doesn't download files, pin files for offline use, or mount the project by itself if the mount is inactive. Offline availability requires deliberate pinning. The sidebar is useful because it gives editors a stable one-click entry point, but it shouldn't be treated as an offline or sync guarantee." }, { "question": "How should teams choose the Aspect cache location and size?", "answer": "Choose a cache location based on the workstation storage plan. A fast internal SSD may work well on an edit bay with plenty of space, while a laptop may need a dedicated external SSD to avoid filling the system drive. Size should match the media workload. Short compressed files may need less cache, while longform, multicam, RAW, or interview workflows usually benefit from more room. Cache improves repeated and nearby access, but it isn't the same as offline pinning." }, { "question": "What is Open in mount used for?", "answer": "Open in mount lets a user start from an asset in the Aspect app and jump directly to the corresponding file on the mounted drive in Finder. It's useful when someone finds an asset through metadata, transcript, review context, or AI search and then needs the actual file path for import, relink, drag and drop, or nearby folder context. It depends on the relevant project or folder being mounted and on the user having permission to access the asset." }, { "question": "What does the Aspect Finder extension add to the workflow?", "answer": "The Aspect Finder extension adds Aspect-aware actions inside Finder. Users can pin files or folders for offline use without switching back to the Aspect app, and they can open a selected file in the Aspect desktop app to see review notes, metadata, versions, approvals, and other asset context. If the extension isn't visible, the exact place to enable or inspect Finder extensions varies by macOS version, so operators should check the Mac's System Settings for Extensions or Login Items and Extensions, then confirm the file is inside the mounted Aspect area." }, { "question": "What should happen when someone finds a file in Finder but needs to know whether it is the approved version?", "answer": "Finder can show the file path and filename, but approval state, comments, versions, metadata, and history should live with the asset record. The Aspect Finder extension lets a user open the selected file in the desktop app so they can inspect the asset context, including version stacking and the broader review workflow." } ], } When editors already live in Finder, forcing every file decision through a browser slows the day down. Mounting Aspect on macOS puts the shared media library where editors, assistants, producers, and post supervisors already touch files: Finder, open dialogs, NLE import windows, relink panels, and folder-based handoffs. Aspect connects to a Mac like a shared network drive. A user mounts a project or folder, then works with that mounted file space from Finder while Aspect [streams the bytes needed](https://www.ycombinator.com/launches/QTB-aspect-intelligent-media-storage-for-creative-teams) on demand and caches them locally. For post supervisors, the important part is deciding which work belongs in Finder, which work belongs in the Aspect app, and how to configure the mount so it behaves predictably for editors. ## What a mounted Aspect project looks like in Finder Once a project or folder is mounted, [Finder treats it like](https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFileSystem/Articles/FilesAndFinder.html) a drive or shared file location. The user sees familiar folders and files, not a separate “media portal” UI. That means normal Finder habits still apply: list view, column view, gallery view, Quick Look, drag into an NLE, right-click actions, file open dialogs, and path-based relinking. The mounted area represents the Aspect project or folder the user chose to mount. If the team mounts a whole project, Finder shows the folder structure in that project from the mount. If the team mounts a narrower folder, Finder starts from that folder instead. That distinction matters for editors because it controls how much of the shared file space appears in their local working environment. A mounted project is useful when the editor needs context across a whole job: camera originals, proxies, graphics, audio, project files, exports, and delivery folders. A mounted subfolder is cleaner when the editor only needs one episode, one day of camera cards, one client deliverable folder, or one offline pack. From a post supervisor’s point of view, the team should use the Finder mount as the place where production files are opened and managed. The Aspect app remains the place for review, approval, metadata, search, and permissions. Finder is where the team opens files and moves them through creative tools. Aspect is where the team understands what the asset is, who can access it, what version is current, what notes are attached, and how it should be governed. ## Make the Aspect drive one click away If a mounted Aspect project is something a user opens every day, put it in the Finder sidebar. Apple’s Finder documentation describes the sidebar as a place to add frequently used items for faster access, and adding an item there creates a shortcut rather than moving the original. For an Aspect workflow, that means the post supervisor can make the mount feel like a normal studio drive: - The Aspect drive or mounted project appears in Finder. - The user drags it [into the Finder sidebar](https://www.youtube.com/watch?v=Z4sOc9vaRIk) under Favorites or the appropriate sidebar section. - The sidebar item becomes the one-click entry point for that project. - The underlying Aspect mount stays where it's. The sidebar entry is just a shortcut. This is a small setup detail, but it prevents a lot of friction. Editors shouldn't have to remember where the mount appeared, browse through Locations every time, or ask an assistant for the path before importing media. If “Client A Post” or “Aspect Projects” is always in the sidebar, the mount becomes part of the workstation muscle memory. If the mounted drive isn't visible in Finder, check the usual macOS visibility settings before assuming Aspect is unavailable. Finder settings control which locations appear on the desktop and in the sidebar. Teams that keep desktops clean may not show external or network-style drives on the desktop, but the mounted location can still be available from a Finder window or sidebar. For shared workstations, make sidebar setup part of the workstation profile. A machine used by multiple editors shouldn't depend on one person’s memory of where the drive lives. Pin the expected Aspect entry once, keep naming consistent, and make sure the path used by edit projects stays stable. ## Cache settings decide how local storage gets used Aspect streams files instead of requiring a full download before work starts. When an editor opens a large clip, Aspect serves the bytes being requested and uses local cache so playback and repeated access don't constantly re-pull the same data. Aspect also prefetches data ahead of what the user is likely to need, which helps reduce waiting during normal media work. That makes cache configuration an operational choice. The cache has two settings that matter most: - Where Aspect stores cached data on the Mac or attached storage. - How much local space Aspect can use for cache. The right location depends on the workstation. On an edit bay with a fast internal SSD and plenty of free space, the internal drive may be the simplest option. On a laptop with limited storage, a dedicated external SSD can keep the system drive from filling up. On a facility workstation, post supervisors may prefer a known local media cache volume so support staff can monitor capacity and avoid mixing cache with OS, application, or project-file storage. | Workstation pattern | Cache location to consider | Cache size posture | Operational note | | --- | --- | --- | --- | | Edit bay with a fast internal SSD and plenty of free space | Internal SSD | Medium to large, based on active project size | Simple for users, but leave room for macOS, applications, renders, and exports. | | Laptop with limited internal storage | Dedicated external SSD | Sized for current jobs and expected travel use | Keeps the system disk from filling up. Confirm the SSD is connected before starting heavy work. | | Facility workstation with support staff | Standard local media cache volume | Consistent size across similar rooms | Easier to monitor, document, and support across edit bays. | | Short-form team using compressed media | Internal SSD or shared workstation cache volume | Smaller limit may be enough | Repeated access still benefits from cache, but the working set is usually smaller. | | Longform, multicam, RAW, or interview-heavy workflow | Fast SSD with generous free space | Larger limit | Gives Aspect more room to retain commonly accessed file ranges between sessions. | | Travel or field work that must survive disconnection | Cache location is not enough | Use offline pinning, not just cache | Cache is opportunistic. Pin required files or folders before leaving the network. | The size limit should reflect the media pattern. A social team cutting short compressed files may not need a huge cache. A longform team scrubbing multicam originals, RAW footage, or long interview selects should give Aspect more room so commonly accessed ranges stay local. If the cache is too small, the mount still works, but the system has less room to retain useful data between sessions. If the cache is too large for the disk, users can run into normal macOS storage pressure. Don't confuse cache with offline pinning. Cache is opportunistic, and Aspect manages it within the configured limit. It helps active work feel fast, but it isn't the same as telling Aspect “keep this file available no matter what.” Offline pinning is the deliberate choice when a user needs files or folders fully available without a connection. This distinction is especially important for travel and field work. If an editor opens a clip at the office, Aspect may cache some data locally, but that doesn't mean the whole folder is safe for a flight. If the laptop needs to work offline, the editor should pin the required assets or folders before disconnecting. ## Use Finder for file work, use Aspect for asset context Finder is excellent at file navigation. Apple’s own Finder guidance focuses on viewing, accessing, organizing, sorting, arranging, previewing, and searching files on the Mac. That makes it the right surface for a lot of daily post-production work. Finder is a good fit for tasks like: - Importing clips into Premiere Pro, Final Cut Pro, DaVinci Resolve, After Effects, Audition, Pro Tools, or another local app. - Relinking a timeline to media paths on the mounted Aspect drive. - Opening stills, audio files, scripts, XMLs, project files, and reference folders. - Using Quick Look to confirm the file before dragging it into another app. - Browsing folder structure when the user already knows where the asset lives. Aspect is the better surface when the user needs meaning around the file, not just the file itself. That includes frame-accurate comments, approvals, version history, custom metadata, and transcription. That split keeps the workflow clean. Editors don't need to leave Finder just to open media in their timeline. Producers don't need to dig through Finder folders just to see the current approved edit or read review notes. Assistants can move between both depending on the job: Finder for relinks and folder checks, Aspect for metadata, versions, access, and search. ## Open in mount closes the gap from app to file Sometimes the user starts in the Aspect app because they searched for an asset, reviewed comments, checked metadata, or found a clip through AI search. Once they have the right asset, the next move may be file-based: open it in Finder, drag it into an NLE, reveal nearby files, or confirm the exact mounted path. That's what open in mount is for. From an asset in the Aspect app, open in mount jumps directly to the corresponding file on the mounted Aspect drive. This matters because search and file navigation answer different questions. In the Aspect app, a user might find footage by [spoken words, people, objects](https://aspect.inc/features/asset-intelligence), scene descriptions, folders, or custom metadata. Finder usually depends more on path, filename, tags, and local file attributes. If the user finds the right moment through Aspect metadata and search, open in mount prevents the annoying second search in Finder. A common post supervisor pattern looks like this: - Producer or assistant finds the asset in Aspect using metadata, transcript, or visual search. - They use open in mount to reveal the file in Finder. - Finder shows the asset in its folder context on the mounted drive. - The editor drags that file into the NLE or uses the path for relinking. The important caveat is that open in mount assumes the relevant project or folder is mounted and the user has access. If nothing happens, or if Finder can't reveal the file, first confirm the mount is active and the user’s permissions include that asset. If the asset lives in a project the user hasn't mounted, mount the project or containing folder before relying on the jump. ## The Finder extension keeps common actions in context Aspect’s Finder extension adds Aspect-aware actions directly inside Finder. This is the inverse of open in mount. Instead of starting in the Aspect app and jumping to Finder, the user can start in Finder and jump back into Aspect context. The Finder extension supports two especially useful actions for post supervisors: - Pin assets for offline use without leaving Finder. - Open any file in the Aspect desktop app to switch context. Apple’s Finder Sync extension framework is designed for this general class of integration: apps can monitor specific folders, [add contextual menu actions](https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/Finder.html), show sync-related UI, and [bridge Finder selections](https://developer.apple.com/documentation/findersync/fifindersynccontroller) back to the app. For Aspect users, the practical result is that the mounted drive can include Aspect actions where file work is already happening. Offline pinning from Finder is the big one for travel and unreliable connections. If an editor is looking at the exact folder they need, they shouldn't have to switch apps, search for the same folder again, and then pin it. They can pin the files or folders from Finder while they're already inspecting the structure. Opening a file in the Aspect desktop app is just as important for review and metadata. If a user is staring at `EXPORT_V12_FINAL_final2.mov` in Finder and needs to know whether that's actually the approved edit, Finder alone may not answer the question. Opening the file in Aspect brings them to the asset context where versions, comments, approvals, metadata, and history live. The extension is also a useful training tool. It teaches the team that Finder and Aspect have complementary roles. Finder is for file work. Aspect is for asset context. The extension lets users cross that boundary without losing the object they were looking at. ## Where this touches editing, review, metadata, access, and archive The Finder integration is most visible in editing, but post supervisors should think about it across the whole workflow. For editing, the mount gives NLEs a normal file path. Editors can import, relink, open project files, and browse bins of media from Finder. Because Aspect streams and caches bytes as needed, the user doesn't need to wait for a full file download before starting work. For review, Finder is usually not where decisions should live. A user can open a file from Finder, but the team should keep comments, annotations, approvals, and versions connected to the asset in Aspect. If someone finds an edit in Finder and needs to inspect feedback, the Finder extension can open it in the Aspect desktop app. For metadata, Finder filenames and folders aren't enough for most media libraries. Aspect can use custom metadata fields for things like campaigns, clients, approval status, regions, SKUs, or other production-specific attributes. Finder can help a user locate a path, but Aspect is the place where your team governs the descriptive layer that makes assets reusable. For access, Finder reflects what [the mounted user can reach](https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemDetails/FileSystemDetails.html). Post supervisors shouldn't use local Finder habits as a substitute for permission design. Post supervisors should manage project, folder, and asset access in Aspect so users only see and work with what they're allowed to use. For archive, Finder shouldn't become a shadow archive process. Aspect supports archiving assets and projects for long-term storage while preserving previews, metadata, and AI access. If a project is done, decide its archive state in Aspect rather than leaving old folders mounted forever on editor machines. ## Boundaries to make clear to the team The Finder mount is intentionally familiar, but it still has cloud-backed behavior. Teams avoid confusion when post supervisors explain the boundaries up front. The main boundaries are: - A mounted file isn't necessarily fully downloaded. - Cache isn't the same as offline pinning. - Finder search isn't the same as Aspect AI search. - Finder folders don't replace Aspect permissions or metadata. - A sidebar shortcut doesn't mount a project by itself if the mount isn't active. Those points sound basic, but they prevent the most common misunderstandings. If a user assumes every visible file is already local, they may be surprised offline. If they assume a cached clip is pinned, they may board a flight without the media they need. If they assume Finder search can find spoken words or visual concepts, they may miss assets that Aspect can find through transcription and metadata/search features. ## Signals that the workflow is working A healthy Aspect plus Finder setup is easy to recognize. The mount is visible, the sidebar entry is obvious, NLEs can browse the path, cache storage isn't crowding the system drive, and users can cross between Finder and the Aspect app without searching twice. Look for these signals during rollout: - The expected Aspect drive or mounted project appears in Finder. - Opening a file from the mount starts quickly enough for the media type and connection. - Cache location and size match the workstation storage plan. - Users pin offline-required files, not merely open them once. - Review notes, approvals, metadata, and versions remain in Aspect rather than drifting into filenames. If those signals are in place, the integration is doing its job. Editors get the Finder-native file workflow they already know. Post supervisors keep control over storage, cache, access, review context, metadata, and archive state. The team moves between local creative tools and the shared Aspect library without forcing unnecessary downloads or duplicates.