Plume
Journaling Apps That Work
With Local AI (2026 Guide)
Here's the honest answer up front: no journaling app bundles a local model, and none should pretend to. You run the model. What separates the apps is whether they can be pointed at the model you're running. A few can: Plume's Mac app takes a custom OpenAI-compatible base URL, so http://localhost:11434/v1 sends your entries straight to Ollama and nothing leaves your Mac. Apps that only hand you a plain-text export are a step behind that, and cloud-only AI isn't local AI at all. This guide ranks them on exactly that.
"Local AI" here means models running entirely on your own machine: Llama 3, Mistral, Gemma, Qwen and similar open models served by Ollama, LM Studio, or a llama.cpp server. All three expose an OpenAI-compatible HTTP endpoint on localhost, which is what lets an app talk to them without a vendor in the middle.
What does "works with local AI" actually mean?
This local-server workflow has two parts: a model runner and the journal content you send it. Ollama, LM Studio, and llama.cpp all serve an OpenAI-compatible endpoint on localhost in a couple of minutes. The app's job is the other half, and it can do it in one of two shapes. The direct shape: the app sends the entry to your localhost endpoint itself, no files involved. The indirect shape: the app hands you clean plain text and you pipe or paste it in. The direct shape is less friction and fewer copies of your journal lying around; the indirect shape works with anything and needs no configuration at all.
Four properties decide whether an app is local-AI-friendly:
- A configurable endpoint. Can you tell the app where the model lives? An app that accepts an arbitrary OpenAI-compatible base URL can be aimed at localhost. One hard-wired to a vendor's cloud can't, no matter how good its AI is.
- Local, open storage. If your entries only live on a vendor's servers, every AI workflow starts with a slow, lossy bulk export, if export exists at all.
- Plain-text export (or plain-text storage). Models eat text. Markdown files, plain-text export, or a readable local database beat proprietary blobs and PDF dumps every time.
- Range selection. Local models have finite context windows. Being able to export exactly "June 1 to June 30" instead of your entire journal makes the difference between a clean prompt and an unusable one.
Rank apps on those four criteria and the list looks very different from a general "best journaling app" ranking. Polished cloud apps drop to the bottom; plain-text tools and local-first apps rise to the top, and the apps that can dial localhost themselves sit at the very top.
The best journaling apps for local AI, ranked
Plume
Talks straight to Ollama or LM Studio on your Mac, with plain-text export as the fallback
Why it ranks first
- On a Mac, open Settings > AI Assistant and configure a local server such as Ollama or LM Studio using its OpenAI-compatible endpoint and exact model name. Plume sends the selected content to that endpoint. AI settings also exist on iPhone and iPad, but localhost refers to the device running the app: a Mac server is not local to your phone. Keep the model and endpoint local for this workflow.
- Use the entry's AI actions to run a configured prompt. Check Settings > Shortcuts for the current keyboard bindings.
- ✓ Off by default, keys in the Keychain: the whole feature is a toggle, and with it off Plume makes no AI network calls at all. If your provider needs an API key it goes into the macOS Keychain, never a plain-text config file. A local endpoint usually needs no key in the first place.
- ✓ The manual path still exists: entries live in a local SQLite database, and you can export any date range as plain text (or encrypted), choose which sections to include, or copy a single entry to the clipboard. No export fee, no lock-in, nothing to configure.
- ✓ Structure helps the model: Plume's dated, sectioned entries give an LLM clean signposts. A month of "Gratitudes / Memory / Accomplishments" is far easier for a 7B model to summarize than a wall of undated prose.
- ✓ Face ID / Touch ID lock, works fully offline, $19.99/year or $59.99 one-time after a free trial of 21 writing days.
Honest limitations
- AI settings are available on Mac, iPhone, and iPad. This guide's localhost workflow runs the model on the same Mac as Plume; a phone does not reach your Mac by using localhost.
- ○ Plume bundles no model and runs no AI service. There's no Plume model and no Plume API key, so this local-server workflow requires a model runner. Apple Intelligence summaries are a separate option on supported devices. That's the trade for never routing your journal through us.
- ○ Export is a copy-out flow inside the app, not a live folder of Markdown files. If you want an always-current file tree for a scripted pipeline, Obsidian or jrnl fit that shape better.
- ○ Apple ecosystem only (Mac, iPhone, iPad), and AI is part of the paid app like everything else after the 21-writing-day trial.
Best for
People who want an actual journaling app (structure, prompts, calendar, streaks) rather than a text editor, and want the local model wired in where they write instead of in a terminal. See the full walkthrough in how to analyze your journal with a local LLM.
Obsidian
Local Markdown files + community local-LLM plugins
Why it ranks high
- ✓ Your journal is just a folder of Markdown files. There is nothing to export; a local model can read the vault directly.
- ✓ The community plugin ecosystem includes plugins that connect to a locally running Ollama or LM Studio endpoint, so you can chat with your notes without leaving the app, and you can point a script at the same vault at the same time.
- ✓ Runs on Windows and Linux as well as macOS and iOS, which makes it the strongest local-AI option outside the Apple ecosystem.
- ✓ Free core app; Daily Notes gives you a dated journal structure.
Where it falls short
- ✗ It's a knowledge tool, not a journal. No gratitude structure, no streaks, no biometric lock without plugins. Expect real setup work.
- ○ Community AI plugins vary in quality and some default to cloud APIs; check that yours points at a local endpoint before pasting anything sensitive.
Best for
Tinkerers who already live in Obsidian and want their journal inside the same vault their local LLM reads.
jrnl
Free open-source CLI journal, plain text, pipeable
Why it ranks high
- ✓ The purest local-AI pipeline that exists:
jrnl -from 2026-08-01 -to 2026-08-31 | ollama run llama3 "Summarize my month"is one line in a terminal. - ✓ Plain text on disk, free, open source, scriptable with cron for weekly AI summaries.
Where it falls short
- ✗ Terminal-only. No calendar, no phone app, no photos, no prompts. If a blinking cursor in a shell doesn't sound like journaling to you, it isn't.
Best for
Developers and terminal natives who want journaling and AI analysis in the same pipe.
Logseq
Free, open source, local Markdown/org files, daily-notes-first
Why it makes the list
- ✓ Opens to today's dated page by default, which is the closest a PKM tool gets to a journal out of the box.
- ✓ Local Markdown or org-mode files, so the same "point a local model at a folder" workflow as Obsidian applies, and it's fully open source.
Where it falls short
- ✗ Outline-style bullet writing suits task capture more than reflective prose, and the AI plugin ecosystem is smaller than Obsidian's.
Best for
People who want free, open-source, local files and think in outlines.
Why don't Day One, Apple Journal, and Journey make the cut?
Day One: has AI, but it's cloud AI
Day One offers AI features on its Gold plan. For a local-model workflow, export selected entries as text or JSON and process them with your own runner. Export is included in Basic; on Mac, select or filter entries before exporting. A Day One subscription is not required just to export your writing.
Apple Journal: export before analysis
Apple Journal is free on supported Apple devices and supports exporting entries. Prepare the exported content as text for your local model. This is a manual workflow; this guide has not verified a built-in custom local-model endpoint in Apple Journal.
Journey: cloud-first by design
Journey (~$29.99/year) is built around cloud sync via Google Drive and its own cloud, with an account required. Export exists, but the app's center of gravity is the vendor's infrastructure, and its AI-adjacent features follow the same cloud pattern. Workable if you must have Android and web; not what you pick for a local-AI workflow.
Local-AI friendliness, compared
The columns that decide whether an app fits a local pipeline: where the data lives, how you get it out, and whether the app can dial your local model itself. Verified as of September 2026.
| App | Data format | Plain-text export | Works offline | Local-AI pipeline |
|---|---|---|---|---|
| Plume | Local SQLite on device | Any date range, choose sections, free | ✓ | Direct: custom OpenAI-compatible base URL → localhost (model running on the same Mac). Export → paste/pipe also works |
| Obsidian | Local Markdown files | Already plain text | ✓ | Direct via community plugins pointed at localhost, or read the vault files; cross-platform |
| jrnl | Local plain-text file | Already plain text, pipeable | ✓ | Trivial (one shell pipe) |
| Logseq | Local Markdown / org files | Already plain text | ✓ | Easy (direct file access) |
| Day One | Local storage with optional Day One Sync | JSON/TXT/PDF export; date selection varies by platform | ✓ | Indirect only: its own AI is cloud-only, no endpoint setting |
| Journey | Cloud (Google Drive / Journey Cloud) | Export exists, cloud-centric flow | Partial | Indirect only, and the export flow is cloud-centric |
| Apple Journal | Encrypted, closed (iCloud/on-device) | Export supported; convert exported content for local AI | ✓ | Manual path: export, prepare the text, then analyze locally |
Formats and export behavior verified against each app's documentation as of September 2026. Export options change; check current versions.
How do I actually run local AI on my journal?
Here's the whole thing using Plume and Ollama on a Mac. Ten minutes, start to finish, and nothing leaves your machine. (For the long version with model recommendations and more prompts, read our full guide to analyzing your journal with a local LLM.)
Install Ollama and pull a model
Download Ollama from ollama.com (free), then pull an open model. Llama 3 8B is a good default on any Apple Silicon Mac with 16 GB of RAM; Gemma or a 3B–4B model works on 8 GB machines. Ollama then serves an OpenAI-compatible API at http://localhost:11434/v1.
Point Plume at it
In the Mac app, open Settings > AI Assistant and configure your local server's OpenAI-compatible URL and exact model name. A local server may not require a key; if your endpoint requires one, Plume stores it in the device Keychain.
From here, requests go from your Mac to your Mac. Plume runs no AI service of its own, so there is no middle hop to trust.
Write, then ask
Edit the three prompt presets to whatever you actually want asked of your journal, and choose per preset whether the answer is appended to the entry or replaces it. Then run them from the Zen Mode AI toolbar, the Today view, or the calendar entry editor:
- Use the entry's AI actions to run a configured prompt. Check Settings > Shortcuts for the current keyboard bindings.
- Choose an AI action for the entry content you want to process; prompts can append output or replace text according to their settings.
Turn the whole feature off in Settings and Plume makes no AI network calls at all. It ships off by default.
Or skip the setup: export and pipe
The manual path is still there and still free, and it's the one to use for whole-month analysis or if you'd rather configure nothing. Open Plume's export view, pick a date range, choose which sections to include, copy the plain text, then feed it to the model yourself:
Prefer a chat window over a terminal? LM Studio does the same thing with a graphical interface: load a model, paste your export into the chat, ask the same questions. One-click copy of a single entry works the same way for a quick question.
Plume has optional AI settings on Mac, iPhone, and iPad. You can choose a supported provider or an OpenAI-compatible endpoint; provider API keys are stored in the device Keychain. For local inference on a Mac, run a local model server and point Plume at its localhost endpoint. Cloud providers receive the entry content included in your request. Apple Intelligence summaries are also available on supported devices when enabled.
Should you ever send your journal to cloud AI?
A journal is about the most sensitive document you own: health worries, relationship friction, work grievances, names of real people who never agreed to be in a dataset. This cuts both ways for an app like Plume that lets you choose the endpoint: point it at localhost and nothing leaves the machine, but point it at a hosted provider and you've opted into everything below. Before pasting your journal into ChatGPT or Claude, or configuring a cloud provider in any journaling app, be clear about what happens:
- Your words leave your device and are processed on company servers, subject to that company's retention policies, staff access rules, and legal exposure.
- Training defaults vary. On consumer ChatGPT plans, as of September 2026, conversations can be used to improve models unless you disable "Improve the model for everyone" or use a Temporary Chat; Team and Enterprise plans default to no training. Other providers have their own toggles. Settings change; check them the day you paste.
- You can't un-send. Once a journal entry has been uploaded, deleting the chat doesn't reliably undo whatever processing already happened.
That doesn't make cloud AI useless for journalers. It's dramatically more capable than a 7B local model, and for low-stakes material (a redacted excerpt, entries with names stripped) it can be a good trade. We've written a separate guide on doing that as safely as possible: how to use ChatGPT with a private journal. The rule of thumb is simple: local AI for the raw journal, cloud AI only for what you'd be comfortable emailing to a stranger.
Frequently asked questions
Do any journaling apps have a built-in local AI?
For this workflow, you run a local model server and connect Plume to its OpenAI-compatible endpoint, or use a compatible Obsidian plugin. Exporting entries to text is another option. Plume also supports Apple Intelligence summaries on compatible devices; that is a separate on-device feature.
What makes a journaling app good for local AI?
Four things: entries stored locally rather than only in a vendor's cloud; a settable endpoint, so the app itself can talk to a model on localhost; a clean plain-text or Markdown export with no fee or lock-in as the fallback; and control over exactly which date range you share, since local models have finite context windows. That's why Plume, Obsidian, jrnl, and Logseq top this list while polished cloud apps don't.
Can I use Day One with a local LLM?
You can export Day One entries and analyze them with a local model. Date-range export is available on iOS and Android; on Mac, use entry selection or filters before export. This guide has not verified a built-in custom local-model endpoint in Day One.
Is it safe to paste my journal into ChatGPT or Claude?
It depends on settings and stakes. Cloud AI sends your words to company servers, and consumer plans may use them for training unless you opt out (in ChatGPT, disable "Improve the model for everyone" or use a Temporary Chat, as of September 2026). For genuinely sensitive material, a local model through Ollama or LM Studio never sends a byte off your machine. Our ChatGPT + private journal guide covers the safer workflow in detail.
What hardware do I need to run a local LLM on my journal?
Any Apple Silicon Mac (M1 or later) with 16 GB of RAM comfortably runs 7B–8B models like Llama 3 8B, Mistral 7B, or Gemma via Ollama or LM Studio; 8 GB Macs can run smaller 3B–4B models. Journal analysis is mostly reading rather than long generation, so modest models still produce useful summaries and pattern-spotting.
Does Plume have AI features built in?
Plume has optional AI settings on Mac, iPhone, and iPad. You can choose a supported provider or an OpenAI-compatible endpoint; provider API keys are stored in the device Keychain. For local inference on a Mac, run a local model server and point Plume at its localhost endpoint. Cloud providers receive the entry content included in your request. Apple Intelligence summaries are also available on supported devices when enabled.
Your journal, your data,
your choice of AI
Plume keeps every entry in a local database, connects to whatever model you point it at — including one running on your own Mac — and exports any range as plain text. Free for 21 writing days, then $19.99/year or $59.99 once. No account needed.