Back to blog
9 min readJuly 5, 2026

One AI search across your notes, screenshots, and messages

A thing you saved is in a note, or a screenshot, or a message you sent yourself. Three places, three searches, and none of them talk to each other. Here is the fix.

Gregory PotemkinProduct Engineering @ dEssence
One AI search across your notes, screenshots, and messages

One AI search across your notes, screenshots, and messages

The thing you saved is in one of three places: a note you typed, a screenshot in your camera roll, or a message you sent to yourself. The problem is you do not remember which. So you search three apps, with three different search boxes, none of which talk to each other. One ask across all of them, including the text trapped inside the images, is the whole point.

This is the quiet tax of saving things in 2026. Capture got easy. You can screenshot a paragraph, type a note, or paste a link into a chat in under a second. Retrieval did not keep up. Each surface keeps its own little pile, walled off from the others, and your memory of where you put something is the only index that spans them. When that memory blanks, the thing is effectively gone even though you saved it on purpose.

It is worth being precise about why this happens, because the usual advice, pick one app and put everything there, fails the moment you live a normal digital life. You will keep screenshotting in the moment. You will keep firing links into a group chat. The split is not a discipline problem. It is built into how the tools are designed.

Why your saves end up in three separate piles

Think about how a single afternoon scatters things. A friend recommends a restaurant in a chat, so the recommendation lives in that thread. You read an article and jot a line in your notes app. You see a chart you want to remember, so you screenshot it, and now it is one of a few thousand near-identical thumbnails in your photos. Three saves, three surfaces, zero connection between them.

Each app searches only its own pile, and each searches it differently. Your notes app does literal text matching on words you typed. Your messages app searches message text but treats a forwarded link as a blob. Your photo library, as of 2026, can find some text inside screenshots, because both Apple and Google now run on-device text recognition, but it searches only photos, and only if you recall the exact words printed in the image.

So even in the best case, you are running the same query three times in three boxes and stitching the results together in your head. More often you do not even get that far, because you cannot remember which of the three holds the thing. Was the apartment listing a screenshot, or a link I sent myself, or did I paste it into a note? That single uncertainty is enough to make you give up and search the open web again, re-finding something you already had.

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <link href="https://fonts.googleapis.com/css2?family=Playfair+Display:wght@400;500&family=Inter:wght@400;500;600&display=swap" rel="stylesheet"> <style> :root{--accent:#0c1e3a;--coral:#F26849;--soft:#f7f5f0;--rule:#e2e2e2} *{box-sizing:border-box} body{font-family:Charter,Cambria,Georgia,"Times New Roman",serif;max-width:760px;margin:0 auto;padding:8px 24px 24px;color:#1a1a1a;line-height:1.65;background:#fff;font-size:17px} .failure-grid{display:grid;grid-template-columns:1fr;gap:14px;margin:22px 0 24px} @media(min-width:640px){.failure-grid{grid-template-columns:1fr 1fr}} .failure-card{background:var(--soft);border-left:4px solid var(--coral);padding:18px 18px 14px;border-radius:4px;position:relative} .failure-card .num{position:absolute;top:-10px;left:14px;background:var(--coral);color:#fff;width:28px;height:28px;border-radius:50%;display:flex;align-items:center;justify-content:center;font-weight:700;font-size:0.92em;font-family:ui-sans-serif,system-ui,sans-serif} .failure-card h4{margin:6px 0 6px;color:var(--accent);font-size:1em;font-family:Charter,Georgia,serif} .failure-card p{font-size:0.94em;margin:0;color:#2a2a2a} </style> </head> <body> <article> <div class="failure-grid"> <div class="failure-card"><span class="num">1</span><h4>The note you typed</h4><p>Your notes app does literal text matching on words you typed, and nothing else.</p></div> <div class="failure-card"><span class="num">2</span><h4>The screenshot you took</h4><p>Now one of a few thousand near-identical thumbnails, searchable only if you recall the exact words printed in the image.</p></div> <div class="failure-card"><span class="num">3</span><h4>The link you sent yourself</h4><p>Buried in a chat thread that treats a forwarded link as a blob.</p></div> <div class="failure-card"><span class="num">4</span><h4>The one index that spans all three</h4><p>Your own memory of where you put it. When that blanks, the thing is gone even though you saved it.</p></div> </div> </article> </body> </html>

What one search across everything would actually need

If the failure is three siloed piles searched three ways, the fix has a clear shape. It is not a better notes app or a tidier camera roll. It is a single layer that sits over all your saves and answers one question against every surface at once. To do that it has to clear a few bars that no single-surface tool clears today.

It has to read inside images, not just match filenames, so the chart you screenshotted and the receipt you photographed are searchable by what they say, not by the date you took them. It has to span surfaces, so a question reaches your typed notes, your saved screenshots, and the links you fired into chat without you choosing which pile to look in. And it has to take a question the way you actually remember things, in your own words, by meaning, not by the precise string you happened to type six weeks ago.

That last point is the one most tools miss. On-device text recognition is real and useful, but it is still literal. It finds the word you remember being in the image. It cannot find "that thing about sleep and afternoon light" when the screenshot never used the word sleep. Meaning-based recall is a different capability, and it is the one that matches how human memory works: fuzzy, by gist, by association. You do not remember the file. You remember roughly what it was about and roughly when it mattered, and a search that only matches exact strings throws that knowledge away.

There is a second bar that gets missed: the search has to reach saves you made by sending, not just saves you made by filing. A huge share of saving now happens inside chat, a link to a friend, a screenshot to yourself, a voice note in a thread. If the one search cannot see into those, it is missing the surface where modern saving actually lives. Messages are not a side channel. For many people they are the main one.

How dEssence does it across all three surfaces

This is the loop dEssence is built around. You save anything from anywhere, a link, a screenshot, a voice note, a PDF, through three co-equal surfaces: the web app, a Chrome extension, and Telegram. It is not a Telegram bot with a website bolted on. Telegram is just one of three doors into the same memory, which matters because messages are where a lot of saves already happen, and dEssence treats a send to a chat as a real save rather than a stray message.

Everything you save lands in one Library. dEssence reads the text inside your screenshots, so the chart and the receipt become searchable by their contents, and it keeps the link you dropped in chat next to the note you typed, in one place. There are no folders, no tags, no organizing at the moment you save, so the saving stays a one-second motion and the work of making it findable moves off your plate and onto the system.

Then, when you go looking, you ask in your own words. "That apartment listing with the bay window." "The article a friend sent about focus." It surfaces the match across surfaces, and it can assemble a board of related saves around a topic, so a question returns a small set of relevant things rather than a single literal hit. The promise underneath all of it is memory you don't have to maintain. You save it, you forget it, you ask for it later.

What this changes day to day

The practical difference is where the work sits. Today, retrieval is your job. You hold the index in your head, you decide which app to open, you run the same query in three boxes, and you stitch the results together yourself. When that index fails, and it fails often, you fall back to re-searching the open web for something you already owned, which is the most wasteful outcome of all: you saved it, and the save bought you nothing.

With one ask across everything, the retrieval work moves to the system. You describe the thing, and it comes back from wherever it landed, the note, the screenshot, or the chat. The uncertainty that used to end the search, which app did I use, simply stops mattering, because there is one place to ask and one Library behind it. The save finally closes its own loop instead of opening a tab of doubt.

That shift compounds quietly. When you trust that a saved thing will return, you stop saving defensively, re-screenshotting and re-bookmarking the same things because you do not believe the old saves will resurface. The pile grows more slowly, and the part of your mind that kept a running map of where everything was can let go of it.

Honest about dEssence

If you are weighing this against your phone's built-in search or a dedicated app like Raindrop or supermemory, here is the straight version. dEssence is in beta, and free during beta with no card, which also means the experience is still settling and rough edges exist. There is no native iOS or Android app yet, so on mobile you save and search through Telegram or the web rather than a polished home-screen app. The free tier has a cap on how much you can keep archived, so a very large existing pile may not all fit at once. There is no offline mode, so the recall depends on a connection.

Your phone's on-device search has a real edge dEssence cannot match: it works offline and instantly on what is already on the device, with nothing leaving the phone. A tool like Raindrop has a mature, native mobile app and years of polish. What none of them do is take one plain-language question and answer it across your notes, your screenshots, and your chat saves at once. That cross-surface, ask-by-meaning search is the specific thing dEssence is for, and the honest trade is maturity now in exchange for a kind of recall the single-surface tools do not attempt.

Frequently Asked Questions

Q: Can my phone already search text inside screenshots?

Partly. As of 2026, both Apple and Google run on-device text recognition, so your photo app can find some text printed inside screenshots. But it searches only your photos, only by the literal words in the image, and it cannot reach the notes you typed or the links you saved in chat. The cross-surface, by-meaning search is what is still missing.

Q: Do I have to move all my old saves into one app first?

No. The idea is that you keep saving where it is natural, through the web, the Chrome extension, or Telegram, and dEssence collects those into one Library you can ask. You are not migrating years of history into a new silo on day one, though the free tier does cap how much you can keep at once.

Q: How is asking different from regular search?

Regular search matches the words you type against the words in the file. Asking in your own words means you can describe a saved thing by gist, "the chart about remote work," and have it surface even if your save never used those exact words. It matches how you actually remember, by meaning rather than by exact string.

Q: Is it really free right now?

Yes, free during beta with no card. The paid plans, Free, Pro, and Team, exist as the shape of the product, but the beta is open to use without payment while the experience is still being refined.