The file-chore tax nobody budgets for
Every social media operator I know has a version of the same confession: the work that eats the day isn’t the work. It’s the interstitial garbage. Exporting a 400 MB stem pack to a collaborator. Resizing a thumbnail for a profile. Compressing a PDF that’s two megabytes over the email ceiling. Stripping location metadata off a phone photo before it goes into a press kit. None of this is strategy. None of it shows up in a content calendar. But it’s the friction that sits between having the file and shipping the post — and it’s the reason so many of us end up paying for five single-purpose subscriptions we open once a week. Ricly, a new macOS utility from maker Samir BAM, is a bet that the fix isn’t another dashboard but the right-click menu you already have. Here’s what that means for people who move files for a living.
What Ricly actually is, and the problem it’s really solving
Strip away the launch-page framing and Ricly is a Finder extension: you select a file, right-click, and one of 17 tools runs on it. The maker’s own example list is telling — a folder of stems gets uploaded and shared with the link already in the clipboard, three contract PDFs get merged into one, and iPhone HEIC photos get converted to JPG and then stripped of metadata before they go into a press kit. That last sequence is the one I’d underline, because it’s the exact chain a creator runs when they’re assembling a media kit from phone photos and don’t want their home address embedded in the EXIF data.
The stated origin story is a subscription-fatigue story, not a feature story. The maker says he was paying for five separate services — one to send, one to compress, one to convert — each demanding an account and then a monthly plan, and still tab-switching for tasks that take ten seconds. So the design constraint became: put the tool where the file already is, and make the free tier real. Ricly is free to start, and per the maker, everything except Upload & Share runs on the Mac itself — nothing is uploaded unless you deliberately share a file.
That last point is the whole ballgame for anyone handling client assets, unreleased tracks, embargoed campaign creative, or anything under an NDA. I’ve lost count of how many times I’ve watched a social manager drag a client’s unreleased product photo into a random browser converter without a second thought about where that file just went. A local-first tool removes that question entirely. Not “we encrypt it in transit” — it just doesn’t leave the machine. That’s a different category of reassurance, and I’d bet it’s the single most defensible thing about this product.
Why the Finder integration matters more than the tool count
Seventeen tools is a number. The distribution channel is the story. A standalone app — even a great one — competes for a dock slot and a habit. A right-click menu item competes for nothing, because it lives inside a gesture you already perform dozens of times a day. The maker says you can choose which tools show up in your menu, so the right-click stays short, which is the correct instinct: the failure mode of every “Swiss Army knife” utility is a context menu so long it becomes slower than opening a browser tab. Curated menus are how you avoid that.
There’s also a compounding angle the maker leans into: new tools are on the way, in the same menu — nothing to install, nothing to learn. If that holds, the product gets more useful without asking the user to adopt anything new. That’s the same flywheel logic that made browser extensions and Raycast-style launchers sticky — you install once, and capability accretes around a habit you already have.
How it stacks up against the incumbents you’re probably already paying
Here’s where I have to be honest about the competitive set, because “all your file tools in one place” is not an empty category.
On the conversion and compression side, the default answer for most creators is a browser tab — CloudConvert, TinyPNG, Smallpdf, and a dozen SEO-farm clones. They work. They’re free-ish. And they all have the same two problems: your file goes to someone else’s server, and you’re one more tab deep in a browser you’re already using for eight other things. Ricly’s local execution is a genuine differentiator against every one of them.
On the creative side, the comparison is less flattering in one direction and more interesting in another. Canva and CapCut have absorbed enormous amounts of “quick file task” work into their editors — resize this, export that, convert this. But they’re editors. You go to them when you’re making something. Ricly’s pitch is that you go to it when you’re moving something, which is a different moment and arguably a more frequent one. I don’t think Ricly competes with Canva. I think it competes with the five-tab detour you take around Canva when all you needed was a format change.
On the sharing side, WeTransfer is the incumbent the maker is implicitly attacking — and it’s a fair attack. WeTransfer’s free tier has spent years shrinking its transfer limits and pushing people toward paid plans, which is exactly the subscription fatigue the maker describes. Dropbox and Google Drive solve the same problem but require the recipient to have an account or navigate a permission model. Ricly’s Upload & Share, per the maker, produces a link that they download in a browser, nothing to install — which is the correct UX for sending files to collaborators, clients, or journalists who will not make an account for you.
And on the “one app for many small utilities” axis, the honest comparison is Setapp — which bundles dozens of Mac utilities for a flat monthly fee. Setapp is a subscription, which is the thing Ricly is positioning against, but it’s also a mature, curated catalog with real support. Anyone evaluating Ricly should at least know Setapp exists.
The category nobody names: the “just do it locally” movement
There’s a broader shift here that I think is more important than any single product. For the last decade, the default answer to “I need to do X to a file” was a web app. That default is now being challenged from two directions: privacy regulation and user fatigue. Tools like ExifTool have done local metadata stripping for years, and ImageOptim has done local image compression forever — but they’re CLI-or-nerd tools, not right-click-menu tools. The gap Ricly is trying to fill is the gap between “technically possible locally” and “actually pleasant locally.” That’s a real gap. My take: it’s also a gap that gets closed by Apple eventually, which is a risk I’ll come back to.
What creators and social teams can steal from this, whether or not they install it
The most useful thing about a launch like this isn’t the product. It’s the diagnostic question the maker asks at the end of his post: Which file chore still sends you to a browser tab? That’s a genuinely good audit prompt, and I’d run it on your own workflow this week.
Here’s how I’d actually use it. For the next three days, keep a running note every time you leave your normal workspace to do something to a file. Not every time you open an editor — every time you leave to do a file operation. I did a version of this last quarter and the list was embarrassing: HEIC-to-JPG for phone-shot B-roll, PDF merges for client contracts, image compression for blog headers, metadata stripping before anything went into a shared folder, and audio format conversion for podcast clips headed to TikTok or YouTube Shorts. Five chores, five browser tabs, three of them behind logins.
The stealable insight is the menu-curation principle, not the tool. The maker explicitly lets you choose which tools show up, and that’s a discipline that applies to every tool stack you run. Your Buffer or Hootsuite sidebar should not show all twelve networks if you only publish to four. Your Metricool dashboard shouldn’t surface metrics you never act on. Your Later calendar shouldn’t show Pinterest if Pinterest isn’t in your mix. Every tool you add to a surface you look at daily has a cognitive cost, and the best operators are ruthless about pruning.
Why the metadata-stripping tool is the sleeper feature for creators
Of the 17 tools, the one I’d tell every creator to care about is Strip Metadata. Here’s the operational why: phone photos carry EXIF data that includes GPS coordinates, device model, and timestamps. When you post to social platforms, most of them strip this on upload — but the moment you put a photo into a press kit, a media kit PDF, a client deliverable folder, or an email attachment, that metadata goes with it. I’ve seen creators accidentally publish their home address in a downloadable asset more than once. It’s a quiet, boring, high-consequence problem.
The maker’s own workflow — HEIC to JPG, then Strip Metadata, for iPhone photos headed into a press kit — is exactly right, and it’s the kind of two-step chain that a right-click menu handles better than two browser tabs. If you do nothing else with this launch, audit your press kit assets for metadata this week. You can do it with Ricly, with ExifTool, or with a handful of other local tools — the tool matters less than the habit.
The repurposing angle nobody’s connecting yet
The stems example is a music-industry detail, but it generalizes hard to social. Every creator I know is running some version of a repurposing pipeline: long-form video → clips → vertical cuts → thumbnails → captions → a PDF or carousel version for LinkedIn or Instagram. Each stage is a file operation. Cut, convert, compress, rename, resize, strip. If you’re doing those in a browser, you’re paying a tax on every single repurpose — and repurposing volume is the single biggest lever most creators have on output.
I’d bet the real value of a tool like this isn’t any one of the 17 tools. It’s the reduction in context switches per repurpose. Ten seconds per switch doesn’t sound like much until you’re doing forty of them a week.
Where I think Ricly falls short, and who shouldn’t bother
I’m going to be blunt, because the launch page is a launch page and you deserve the other side.
It’s Mac-only. The maker is explicit that the work happens on your Mac, and the Finder integration is the entire premise. If your team runs Windows, or if you’re a hybrid shop, this is a non-starter for anything collaborative. There’s no Windows or web version mentioned in the source — not disclosed whether one is planned. For a solo creator on a MacBook, fine. For a five-person social team on mixed hardware, this fragments your workflow rather than unifying it.
The tool count is a claim, not a track record. Seventeen tools at launch, with new tools on the way. I’ve watched a lot of “Swiss Army knife” utilities launch with a big number and then stall — either the new tools never ship, or they ship shallow. The maker’s stated method for picking what to build next is asking users which file chore sends them to a browser tab, which is a good signal-gathering instinct, but it’s also a signal that the roadmap is genuinely undefined. Don’t buy (or adopt) on the promise of future tools. Adopt on the 17 that exist.
Pricing beyond “free to start” is not disclosed. The maker says free to start, which implies a paid tier, but the source doesn’t say what’s gated, what it costs, or whether Upload & Share — the one feature that isn’t local — is the paid hook. Given that the entire pitch is anti-subscription, the pricing model is the thing I’d want nailed down before I build a habit around it. If it ends up as a $10/month subscription, the pitch collapses into the exact thing it’s criticizing. I’d bet the maker knows this, but the source is silent, so treat it as an open question.
The local-first claim is strong but unverified by me. I haven’t run Ricly myself. The maker’s claim that everything except Upload & Share runs on the Mac is the kind of thing that should be independently verifiable — and for a tool handling client assets, it’s worth verifying before you trust it with anything sensitive. I’d want to see network traffic monitoring on a conversion before I put an NDA’d file through it. That’s not a knock on Ricly specifically; it’s the standard I’d apply to any local-first claim from any maker.
Who it’s not for: teams that need shared tooling and audit trails, anyone on Windows, anyone whose file chores are already fully handled by their editor (if you live inside Adobe Creative Cloud or Final Cut Pro, you may not have this problem), and anyone who needs a support contract. This is a solo-operator utility, and that’s a feature, not a bug — but it’s a narrow lane.
Where the math breaks
The subscription-fatigue pitch only works if Ricly replaces more than it costs. If you’re paying for five tools at $8/month each and Ricly is free-to-start, the math is obvious. But if you’re paying for one $10 tool and Ricly is $10, you’ve just added a subscription to save a subscription. The maker hasn’t published the pricing, so I can’t run the numbers — but you should, before you commit. The honest frame is: this is worth adopting if it eliminates at least two paid tools from your stack, or if local-first execution is worth a premium to you for privacy reasons. Otherwise it’s a nice-to-have.
What I’d watch / test next
If you’re a Mac-based creator or solo social operator, here’s what I’d actually do this week — concretely, not aspirationally.
First, run the audit. For three days, note every time you leave your normal workspace to do something to a file. Don’t change anything yet. Just count. You’ll probably find three to five recurring chores, and that list is your actual spec — not the feature list of any tool.
Second, if the audit surfaces metadata stripping, HEIC conversion, or PDF merging as recurring chores, Ricly is worth a trial on the strength of those alone. Test it on non-sensitive files first, and if you’re going to trust it with client assets, verify the local-first claim yourself with a network monitor before you do.
Third, watch the pricing page. The entire pitch rests on not becoming the thing it’s criticizing. If Ricly ships a reasonable one-time price or a genuinely free local tier, it’s a strong addition to a Mac creator’s stack. If it ships as another $10/month subscription, the pitch and the product are in conflict, and I’d wait.
Fourth — and this is the one I’d actually bet on — watch whether the “right-click menu” model spreads. If Ricly works, I’d expect to see copycats, and I’d expect Apple to eventually absorb the best of these tools into macOS itself. The window for a standalone product in this category may be shorter than it looks. That’s not a reason to avoid it. It’s a reason to adopt it now if it solves a real chore for you, and to not over-invest in it as a platform.
The bigger lesson stands regardless of what happens to Ricly: the file-chore tax is real, it’s unmeasured, and it’s eating your output. Count it this week. Then decide what to do about it.
