The creator stack has a capture problem, and the newest fix is refreshingly dumb
Every social media operator I know is sitting on a graveyard of content ideas. Not because they lack inspiration, but because the capture step is broken. You see a hook in a TikTok comment section, screenshot a competitor’s carousel, save a tweet to a bookmarks folder you’ll never open, and paste a half-formed script into a Notes app that buries it under grocery lists. By the time you sit down to plan a week of content, the raw material has evaporated. That’s the problem put.here is trying to solve, and while it’s a Mac-only note tool from an indie maker named Peter Li, the underlying philosophy is worth stealing for your own content workflow — even if you never install it.
Here’s the thesis: the best content systems separate capture from organization. Most tools do the opposite. They force you to title, tag, and file something the moment it enters your brain, which is exactly when you have the least context about what it’s for. put.here inverts that. You dump first, organize later. For creators who publish across Instagram, TikTok, YouTube, X, LinkedIn, Facebook, Threads, and Pinterest, that’s not a minor UX preference — it’s the difference between a content pipeline that compounds and one that stalls every Sunday night.
What put.here actually does, and why the “no folder” constraint matters
The pitch from the maker is deliberately anti-feature. You paste, drag, or hit a keyboard shortcut (⌃⌥P) from any app, and the thing lands on a canvas. No title prompt. No folder picker. No tag taxonomy. It just sits there. When you return, you step back, look at the pile, and group things by hand. Everything lives as plain files in a folder on your Mac, so if you stop using the app, your notes remain. It’s free to start, Mac only, and requires macOS 14 or later.
That’s the entire product. No AI summarization, no auto-tagging, no “smart” anything. In a creator-tool market saturated with AI-powered everything, that restraint is the story. The team isn’t claiming to 10x your reach or automate your workflow. They’re claiming to remove friction from one specific moment: the moment an idea hits you and you need it out of your head before it disappears.
Why the plain-files detail is the most important line in the pitch
I’ve tested enough note and capture tools to know that lock-in is the silent killer. You spend three months building a swipe file inside a proprietary app, then the company pivots, raises prices, or shuts down, and your entire idea library is trapped in an export format nobody supports. The maker’s decision to store everything as plain files in a folder is a trust signal, not a feature bullet. It means your swipe file, your hook bank, your screenshot archive — all of it is portable. You can open it in Finder, sync it with iCloud or Dropbox, grep it, back it up, or walk away. For a creator whose content library is effectively their business asset, that matters more than any AI feature.
How this fits — and collides — with the tools you already use
If you’re running social for a brand or yourself, your stack probably looks like some combination of Buffer, Hootsuite, Later, or Metricool for scheduling and analytics, Canva for design, CapCut for video editing, and maybe Notion or Airtable for content calendars. Each of those tools solves a downstream problem: publishing, measuring, designing, editing, planning. None of them solves the upstream problem of capture.
That’s the gap put.here is aiming at. It’s not competing with Buffer or Hootsuite — it’s competing with the chaotic mess of Apple Notes, Screenshots folder, Twitter bookmarks, and a graveyard of Slack DMs to yourself. In my experience, that mess is where most content ideas go to die. The tools that handle publishing assume you already have something to publish. The tools that handle capture assume you want to organize while capturing. put.here is betting that the second assumption is wrong.
Where the math breaks
Here’s the limitation, and it’s significant for social media teams. put.here is Mac-only, single-player, and has no sharing, no collaboration, no mobile app, and no integrations with scheduling tools. If you’re a solo creator working on a MacBook, that’s fine. If you’re a social media manager coordinating with a designer, a videographer, and a copywriter across three time zones, it’s a non-starter. There’s no way to hand a canvas to a teammate, no way to turn a cluster of saved links into a brief, and no way to push a captured idea directly into your content calendar. The maker is explicit that this is version one and asks users where it falls short — which is honest, but also a signal that the collaborative layer doesn’t exist yet.
The other open question is search and retrieval. A canvas of hundreds of untitled items is great for visual thinking and terrible for finding that one screenshot you saved six weeks ago. The maker hasn’t disclosed how search works, whether there’s OCR on screenshots, or whether you can filter by file type. Until that’s answered, I’d treat put.here as a front-end capture layer, not a replacement for a searchable swipe file.
What creators and social teams should steal from this, regardless of whether they install it
The most valuable thing about put.here isn’t the app. It’s the workflow principle: capture without categorizing, then organize in batches. I’ve started applying a version of this to my own content operations, and it’s changed how I plan.
Instead of forcing every idea into a platform-specific folder the moment it arrives, I now dump everything into a single inbox — screenshots, links, half-sentences, voice memos — and set aside one 30-minute block per week to sort. During that sort, I’m not just filing; I’m looking for patterns. Three screenshots of the same competitor’s hook format becomes a content angle. Five saved comments about the same pain point becomes a script. The sorting session is where strategy happens, and it only works if the capture step was frictionless.
Why TikTok creators should care more than LinkedIn ones
The half-life of a TikTok trend is measured in days, sometimes hours. If your capture workflow adds friction — if you have to open an app, create a note, pick a folder, and type a title before you can save a sound or a format — you’ll miss the window. put.here’s one-keystroke capture is genuinely useful for fast-moving platforms. LinkedIn, by contrast, rewards evergreen takes and thoughtful commentary. You can afford to let a LinkedIn idea marinate in a messy inbox for a week. The urgency calculus is completely different, and it should shape which tools you prioritize.
The screenshot-drag question is the real product test
In the Product Hunt thread, a user named Jaewon Seo asked whether you can drag the floating screenshot thumbnail that appears after Cmd+Shift+4 — the one in the bottom-right corner — directly into the app. He noted that’s “like 80%” of what he’d want to drop in. The maker replied that he hadn’t thought of it, tried it, found it natural, and said he’d add support in the next update.
That exchange is a microcosm of the whole product challenge. For social media operators, screenshots are the primary capture format. You screenshot a tweet, a TikTok comment, a competitor’s Story, a Slack message from your boss, a Google Analytics dashboard, a trending audio notification. If dragging those thumbnails into the canvas works seamlessly, put.here becomes a genuinely useful swipe-file front end. If it doesn’t, you’re stuck saving to Desktop and then dragging from Finder, which is exactly the kind of friction the app claims to eliminate. The maker says it’s coming, but it’s not there yet — so if screenshot capture is your primary use case, wait for that update before committing.
The bigger picture: why “dumb” tools are having a moment
There’s a pattern here that’s bigger than one indie Mac app. The creator tool market has spent the last two years racing to add AI to everything — AI captions, AI thumbnails, AI repurposing, AI scheduling. And a lot of it is genuinely useful. But there’s a counter-trend: creators are tired of tools that think for them and want tools that get out of the way. The popularity of plain-text note apps, the resurgence of simple bookmark managers, and the appetite for tools like put.here all point to the same thing. People want to own their raw material and do the thinking themselves.
I’d bet this is a durable shift, not a fad. The AI layer is most valuable when it’s applied to a clean, well-organized corpus of your own ideas. If your capture system is a mess, no amount of AI summarization will save you. Fix the input before you automate the output.
Who this is not for
Let me be direct about the limitations, because the maker is honest and I’ll be too. put.here is not for you if:
- You work on Windows or Linux. Mac only, macOS 14+.
- You need team collaboration. No sharing, no multi-user, no permissions.
- You need mobile capture. There’s no iOS app mentioned, which means capturing an idea on your phone — where most of us consume content — isn’t part of the workflow yet.
- You want AI assistance. There is none. No auto-tagging, no summarization, no semantic search.
- You need scheduling integrations. Nothing connects to Buffer, Later, or any calendar.
- You want a polished, feature-complete product. This is version one from an indie maker who is actively asking users what’s missing.
Pricing beyond “free to start” is not disclosed. Whether there’s a paid tier, what it costs, and what it unlocks are all open questions. That’s not a red flag for an early-stage indie tool, but it is a reason to test before you build a workflow around it.
What I’d watch / test next
If you’re a creator or social media operator reading this, here’s what I’d actually do this week — whether or not you download put.here.
First, audit your capture workflow. For the next three days, every time a content idea hits you, notice where it goes. Screenshot? Notes app? DM to yourself? Voice memo? Write down the friction points. You’ll probably find that capture is where your pipeline leaks.
Second, if you’re on a Mac and want to test put.here, install it and run a one-week experiment. Dump everything into the canvas without organizing. At the end of the week, do a single 30-minute sorting session and see whether patterns emerge that you’d have missed in a folder-based system. The maker is explicitly asking for feedback on what didn’t work, so if screenshot-drag isn’t supported yet, tell him — that’s how the product improves.
Third, if you’re on a team or not on a Mac, steal the principle instead. Create a single shared inbox — a Slack channel, a Notion database, a Google Doc — where anyone can dump raw ideas without formatting or categorization. Then schedule a weekly sort. The tool doesn’t matter. The separation of capture from organization does.
Finally, watch whether put.here adds screenshot-drag, search, and any form of export-to-calendar. Those three features would move it from a clever capture toy to a genuine front end for a content operation. Until then, it’s a useful experiment in doing less — which, for a creator stack that’s been drowning in AI features nobody asked for, is a refreshing place to start.
