Features

Images and PDFs, treated as part of the wiki

Hand a photo or a PDF to your agent. It picks the right doc and embeds the file where it belongs.

A wiki that's "mostly text, attachments are a hassle" forces you to choose between writing things down and keeping the picture that explains them. Daneshbase doesn't make you choose.

Drop it into the conversation, the agent does the rest

Hand a photo of a coffee bag, a screenshot of a settings panel, a PDF receipt for last quarter's hardware — your agent receives the file, figures out which doc it belongs in, and embeds it in the right section. You don't manage attachment IDs, paths, or filenames.

Attach once, reference anywhere

The same picture can appear in any number of docs. The bag-of-beans photo lives once in your wiki and gets referenced from your brewing recipe, your bean log, and the running list of things-to-try. No re-uploading, no duplicate copies, no version-skew.

PNG, JPEG, WebP, GIF, PDF

Anything visual within your plan's per-file and total-storage limits. Big files travel directly between your device and storage — they don't pass through the AI's context, so they don't burn tokens.

Permanent

As long as your base exists, every attachment is there. No expiry, no archival tiers, no quietly-pruned old files. When you delete your account everything goes — until then, the image you uploaded in month one is still embeddable in month thirty.

We use a sealed session cookie to keep you signed in and an i18n cookie to remember your language. Our customer-support chat (Crisp) also uses a cookie — if you decline, the chat will not load and you can reach us at hello@daneshbase.com instead.Learn more in our Privacy Policy.