Bloom for Mac

Bloom runs on macOS 14 and above, on both Apple Silicon and Intel Macs. It is a standalone file manager, built by INCHMAN1900, that sits alongside Finder and offers a different way to browse, search, and organise files.

Keyword search across preset locations: your folders, instantly found

• Searching by keyword across predefined locations, not just the current folder
• Previewing archives without extracting them first
• Renaming batches of files with regular expressions
• Scanning folders and viewing disk usage as a treemap
• Launching Terminal directly from the folder you are browsing
• Pinning a Portal window above other windows or docking it at the screen edge

Portal windows stay on top: a deliberate quick-reference tool

• It organises files by type or date, but it is not a media library
• Automatic column resizing is present; manual fine-tuning is still useful
• Portal windows stay on top, which suits quick-reference workflows
• The treemap view is a disk-usage tool, not a replacement for dedicated analysers

Finder stays intact: Bloom works beside it, not instead of it

One common question is whether Bloom replaces Finder entirely. It does not. Finder remains the system’s file manager, and Bloom works beside it as a separate application. You can keep using Finder for anything you already do, and open Bloom when you need its search, renaming, or Portal tools. Another frequent concern is whether the app feels heavy on a Mac. The interface is compact and column-based, and the preview limit of 10 MB keeps large media files from slowing down the window while you browse. People also ask about iCloud Drive. Bloom integrates with it, so files stored in iCloud appear in the same workspace as local folders, provided they are already downloaded or available on demand through the system.

Those who manage many files often ask about safety during batch operations. The app records each operation for undo, which is worth remembering before a large rename or move. If a regular-expression pattern does not behave as expected, the undo history gives you a way back without rebuilding the folder from a backup. Searching for a oeksound bloom download is unrelated to this Bloom, by the way; the name overlap is purely coincidental. This Bloom is a file manager, not an audio plug-in.

Set your daily locations first: skip the folder tree entirely

Begin with the predefined search locations. Instead of browsing deep folder trees, set the locations you actually use every day — a project folder, the desktop, an iCloud Drive workspace — and search by keyword from there. The ⌘⇧⏎ shortcut for jumping to a system location is useful early on, because it removes the need to keep those folders in the sidebar. Once you have used it a few times, it becomes faster than dragging windows around the screen.

Practice the archive preview before you trust it with large collections. Open a few zip or tar archives in Bloom and look at their contents without extracting them. This is particularly helpful when you receive a folder of design assets or exported documents and need to check what is inside before unpacking. The preview also applies to text, images, and PDFs under 10 MB, so it covers most everyday reference material.

If you rename files often, spend half an hour with the regular-expression renaming. Start with a simple pattern — replacing spaces with hyphens, or adding a date prefix — and watch how the preview shows the result before anything is applied. The undo history is your safety net. After a few sessions, batch renaming becomes one of the reasons to open Bloom instead of Finder.

One keyword, one client folder: results across all your workspaces

On a typical afternoon, I open Bloom and search for a client folder by keyword. The results appear across the locations I have defined, so I do not need to remember whether the folder lives in Documents or on iCloud Drive. I press ⌘F to search inside that folder, then refresh with ⌘R when I add a new file from another app.

Next, I inspect a compressed archive that arrived from a collaborator. Bloom shows me the contents without extraction, and I decide which files are worth unpacking. I rename the useful ones in a batch, using a regular expression to clean up the version numbers in their names. Then I organise the folder by type, and Bloom places the images, documents, and source files into a clearer order.

When I need to check how much space a project folder is using, I switch to the treemap view. It gives a quick visual sense of which subfolders are large, without a separate disk analyser. If I want to run a command in that folder, I launch Terminal directly from the current location, which saves the usual cd typing. Before finishing, I convert a few large images to smaller formats, and the whole session is recorded in the undo history in case anything needs to be reversed.

Column resizing refined: predictable widths regardless of file name length

Version 1.5.42 is the current release, and the changes are mostly about stability in everyday use. The automatic column resizing behaves more predictably when switching between folders with very short and very long file names. The Portal window also received attention: pinning and edge docking now feel smoother, and the compact window is less likely to lose its position after a workspace change.

The developer keeps the update process quiet and automatic after installation, so there is no separate updater window to manage. For users who rely on search, the keyword results are more consistent across predefined locations, especially when iCloud Drive is involved. The treemap view remains a lightweight way to spot large folders, and the archive preview still works without extraction. None of these changes alter the core workflow, but together they make Bloom feel less like an experiment and more like a daily tool on macOS 14 and later, on both Apple Silicon and Intel machines.

• macOS 14 or later
• Apple Silicon or Intel 64‑bit processor