Migrating OpenClaw: How to Protect Your Agent’s Memory and Data
How To Update Openclaw On Windows 11: episode overview
This BeFreed audio learning guide explores the process of migrating and updating OpenClaw on Windows 11. We cover the essential steps to locate your agent data, safely back up your configurations, and navigate the update process without losing your AI assistant's memory or API keys.
Create Your Podcast in a Click
Generated by Thomas
Input question
Create a short technical podcast (5–8 minutes) explaining how to migrate from an older OpenClaw installation to the latest version on Windows 11. Cover how to locate legacy OpenClaw data folders, identify which files to back up (profile, settings, agents, API keys, memory), safely uninstall the old version, install the new version, restore the preserved files, and verify everything works. Include common pitfalls and simple PowerShell commands where useful.
Host voices
What you'll learn about How To Update Openclaw On Windows 11
- 1
Don’t Let Your Agent Wake Up with Amnesia
00:0000:00Miles: Hey, so I was looking at my OpenClaw setup earlier today—it’s June 9th, 2026—and I realized I’m still running a version from months ago. I know I need to update to the latest Windows 11 build, but honestly, the thought of losing my agent’s "personality" or all those API keys I painstakingly entered—it’s a little nerve-wracking. I don’t want to start from scratch. Nia: I totally hear you. It’s that classic "if it ain't broke, don't fix it" mentality, right? But with OpenClaw moving as fast as it is—it’s still technically in its pre-1.0 phase—sticking with an old version means you’re missing out on a lot of stability and features . The good news is that you don’t have to lose anything. You just need to think of this update less like a "delete and reinstall" and more like shipping infrastructure—you move the data, verify the pipes, and then flip the switch . Miles: Okay, that makes it sound a bit more professional and a bit less like I’m just rolling the dice. But where do I even start? My files are probably scattered all over my C: drive. Nia: That’s the first hurdle most people hit. You’ve got to know what you’re looking for before you touch that uninstall button. Most Windows users are looking for a hidden folder called `.openclaw` right in their user directory—usually `C:\Users\<YourUsername>\.openclaw` . That’s the "brain" of the operation. If you don't back that up, your agent basically wakes up with total amnesia—no history, no keys, no memories . Miles: A blank slate is exactly what I’m trying to avoid. So, if I find that `.openclaw` folder, is that everything? Or are there other "footguns," as the devs like to call them, waiting to trip me up? Nia: There are definitely a few. For instance, your "workspace"—the place where your agent actually keeps its notes and drafts—might be in a completely different spot if you customized it during your first setup . We’re going to walk through how to map all of that out so when you hit "upgrade," you’re doing it with total confidence. Let’s get into how to actually locate these legacy folders without playing hide-and-seek with your filesystem.
- 2
Mapping the Digital Paper Trail
Miles: You mentioned that `.openclaw` folder in the user directory, but what if I’m one of those people who likes to be "organized" and moved things around? Is there a way to ask OpenClaw itself where it’s keeping its stuff before I pull the plug? Nia: That’s actually the smartest way to do it. Instead of guessing, you can just run `openclaw info` in your terminal or PowerShell . It’ll spit out exactly where the "state directory" is. This is crucial because if you’ve been using the `OPENCLAW_STATE_DIR` environment variable to point to, say, a secondary drive, a standard search of your C: drive won't find it . Miles: Oh, that would have been a disaster. I can imagine myself backing up an empty folder and then wondering where my life’s work went. So `openclaw info` gives me the state directory—what about the workspace? Nia: Usually, the workspace defaults to `~/.openclaw/workspace/`, but the `info` command should give you a hint there, too . Think of the state directory as the "nervous system"—it’s got your config, your auth tokens, and your session history. The workspace is more like the "filing cabinet" where the agent stores its actual work products, like memories and skill notes . Miles: It’s interesting that they’re split up like that. It makes sense, though—one is about how the app runs, and the other is about what the app *knows*. Nia: Exactly. And if you’re running multiple agents or different profiles, you might have multiple state directories, like `.openclaw-dev` or `.openclaw-test` . You’ll want to repeat that check for each profile you care about. Miles: That’s a great point. I definitely have a "test" agent that I use for messing around with new plugins. I’d hate to lose those experiments. But there’s a specific bug I heard about on Windows—something about backslashes in the file paths? Does that affect where I find my data? Nia: You’re thinking of a bug that popped up earlier this year, around March 2026. Some Windows users found that the app was looking for a path like `C:\Users\Username.openclaw`—literally missing the backslash between the name and the folder . While the developers have largely addressed this by using proper path-building tools in the newer versions, it’s a perfect example of why you want to manually verify your paths using `openclaw info` rather than just assuming the default layout is what’s actually being used . If your agent is complaining that it can’t find API keys right now, that path mismatch might be exactly why.
- 3
Identifying the Essential Payload
Miles: Okay, so I’ve found my `.openclaw` folder and my workspace. Now, I’m looking at a sea of files. What do I actually need to grab? I don't want to carry over a bunch of "digital lint" that might mess up the new installation. Nia: It’s a "load-bearing" quartet of data you need to worry about: your Config, Credentials, Sessions, and Workspaces . If you lose the `openclaw.json` file, which is your config, you’re basically rebuilding your entire setup from memory—every agent, every channel, every port you configured . Miles: That sounds like a long Saturday afternoon I’d rather avoid. What about the credentials? Those are always a pain to reset. Nia: Credentials are arguably the most sensitive part. You’ve got two main spots here. First, your LLM provider tokens—like your Claude or OpenAI keys—which are usually tucked away in per-agent auth profiles under `agents/main/agent/auth-profiles.json` . Then you’ve got the `secrets.json` file, which handles third-party stuff like Discord bot tokens or Twitter keys . If you don't migrate those, your agent will boot up but won't be able to talk to anyone. Miles: So it’s like moving into a new house but forgetting your keys and your phone. You’re there, but you’re locked out and isolated. Nia: That’s a perfect analogy. And don't forget the Sessions. That’s your conversation history. If you skip those, your agent effectively wakes up with no context of anything you’ve talked about before . Finally, there’s the Workspace—that’s the `memory` folder and any drafts the agent has been working on . Miles: It’s a lot to keep track of. Is there a way to just... bundle it all together? Nia: There is! OpenClaw actually has a built-in command for this: `openclaw backup create` . It’s designed to be "disaster-recovery ready." It bundles config, credentials, sessions, and your workspaces into a single gzipped tarball . It even creates a manifest file inside the archive so the system knows exactly where everything came from . Miles: That sounds way safer than me dragging and dropping folders in File Explorer. Does it handle those weird Windows path issues we talked about? Nia: It does. It "canonicalizes" the paths—basically simplifying them—before building the archive . So if your credentials folder actually lives inside your state directory, it’s smart enough not to back it up twice . It’s the "pro" way to ensure you’re grabbing exactly what you need and nothing you don't.
- Chapter 4
The Pre-Flight Checklist and PowerShell Prep
**Miles:** I’m sold on the `openclaw backup create` command. But before I run it, is there anything I should do to make sure the backup itself is "clean"? Like, do I need to turn the lights off before I leave the building? **Nia:** Definitely. You really want to stop the gateway before you start copying files. If the gateway is running while you’re backing up, it might be trying to write to a session file or update a log right as the backup tool is reading it, which can lead to corruption . On Windows, the easiest way to do this is through the CLI with `openclaw gateway stop` . **Miles:** Makes sense. Stop the heart before you do the transplant. Now, once I’ve stopped it, what’s the move? Do I just run the backup command and hope for the best? **Nia:** You could, but why guess when you can plan? You can run `openclaw backup create --dry-run` first . This is a "dry run" that won’t actually write any files. It just prints out a list of exactly what’s going to be included and what’s being skipped . It’s your last chance to notice if a custom workspace you spent weeks on is missing from the list. **Miles:** I love a good dry run. So, once the plan looks good, I execute. What does that look like in PowerShell? **Nia:** It’s pretty straightforward. You just run `openclaw backup create --verify` . That `--verify` flag is key—it tells OpenClaw to check the archive immediately after writing it to make sure the data isn't corrupted . If you want to be extra organized, you can specify an output directory with the `--output` flag, like `openclaw backup create -o C:\Backups\OpenClaw` . **Miles:** And if for some reason the built-in backup command fails—maybe my config is super messy or something—is there a manual PowerShell fallback? **Nia:** If the config is so malformed that the backup tool can't even parse it to find your workspaces, you can use the `--no-include-workspace` flag to at least save your state and credentials . Or, if you want to go full manual, you can use a PowerShell command like `Compress-Archive -Path $HOME\.openclaw -DestinationPath C:\Backups\OpenClaw_Manual.zip` . Just remember that the manual way doesn't give you that nice manifest file or the automatic verification that the built-in tool provides . **Miles:** I’ll stick with the built-in tool if I can. It sounds like it’s built to handle the heavy lifting. So, I’ve got my verified archive—a nice, timestamped `.tar.gz` file. Now comes the scary part: actually getting rid of the old version.
Chapter 5The Clean Break and Fresh Start
**Miles:** Okay, I have my backup safely tucked away on my secondary drive. I’m ready to uninstall. Is it as simple as going to "Add or Remove Programs" in Windows, or is there a "cleaner" way to do it? **Nia:** For OpenClaw, the "cleanest" way depends on how you installed it. If you used the website installer, it’s usually best to just run that again—it’s designed to detect existing installs and "upgrade in place" . But since we’re talking about a significant version jump, sometimes a fresh start is better. If you installed via `npm`, you’d use `npm uninstall -g openclaw` . **Miles:** And does that wipe out the `.openclaw` folder in my user directory? **Nia:** Generally, no. Most uninstallers leave your data folders alone just in case you’re doing exactly what we’re doing—upgrading. But here’s the "Pitfall Alert": even if the folders are still there, the *permissions* might get wonky when you install the new version . If the new version runs under a different user context or if the installer changes ownership, the gateway might fail to read your old credentials . **Miles:** That would be a nightmare. "Access Denied" to my own API keys. **Nia:** Exactly. That’s why we take the backup. Even if the old folder stays put, I actually recommend moving that old `.openclaw` folder to a temporary "Old_Data" location once you’ve uninstalled. Start the new installation with a truly clean slate . **Miles:** So, I’ve uninstalled, moved the old data out of the way, and now I’m running the new installer. What am I looking for during the setup? **Nia:** If you’re using the website installer, you can actually add a `--no-onboard` flag if you want to skip the whole "Welcome to OpenClaw" wizard, since you’re planning to restore your old settings anyway . Once the installation finishes, the first thing you should do—before you even try to start the gateway—is run `openclaw doctor` . **Miles:** "Doctor"? Is it going to tell me my installation is sick? **Nia:** Hopefully not! Think of it as a "safe update" command. It’s intentionally "boring"—it just repairs services, migrates deprecated config keys, and checks your gateway health . On Windows, it’s particularly good at detecting and migrating older scheduled tasks to the current service model . It’s the "bridge" between your old setup and the new logic.
Chapter 6Reconstructing the Brain
**Miles:** I’ve got the new version installed, and I ran the "doctor" check. Now I’m looking at a brand new, empty `.openclaw` folder. How do I get my "brain" back in there? **Nia:** This is where you restore from that archive you made. Since there isn’t a single "restore" command yet, you’ll do this part manually, but it’s just a few steps. First, make sure the gateway is stopped on the new install—you don't want it trying to create new default files while you’re overwriting them . **Miles:** Right, `openclaw gateway stop`. Got it. Then I just unzip the archive? **Nia:** Basically. You want the contents of that archive to end up back in `$HOME\.openclaw` . If you’re using the command line, you can use `tar -xzf your-backup-filename.tar.gz -C $HOME\.openclaw` . One thing to watch out for: the archive might have a internal directory structure that includes your old username . You want to make sure you’re moving the *contents* of that backup folder into your *current* `.openclaw` directory, not just nesting a folder inside a folder. **Miles:** Ah, the classic "folder-in-a-folder" trap. I’ve definitely done that with Zip files before. So I should end up with `openclaw.json` and the `agents` folder directly under `.openclaw`, right? **Nia:** Spot on. And here’s a "Pro Tip" for Windows users: if your username changed—maybe you got a new laptop and set it up with a different name—the paths inside your `openclaw.json` might still be pointing to the old user directory . This is another reason why `openclaw doctor` is so important. After you move the files back, run `openclaw doctor` again. It’s smart enough to warn about mismatches. **Miles:** It really is like a little digital medic. What about the workspace? Does that go back in the same way? **Nia:** Yep, same deal. Move your workspace files back to their original path. If you kept the default, that’s usually `~/.openclaw/workspace/` . Once everything is in place, you can finally run `openclaw gateway start` . **Miles:** It feels like the moment of truth. But how do I actually *know* if it worked? I don't want to just assume everything is fine because the terminal didn't explode. **Nia:** That’s where the verification checklist comes in. You want to see if your "identity" is intact. The first thing I always check is `openclaw config`—does it show your agents and your old settings? . Then, check your channels. If you have a WhatsApp or Discord integration, are they still connected, or are they asking you to re-pair? . If you did the migration right, those sessions should still be active and ready to go.
Chapter 7Post-Migration Health Checks
**Miles:** Okay, so I ran the commands, I moved the files, and I started the gateway. The dashboard is up, and I see my agents. But I’m feeling a little paranoid. What’s the "stress test" for a new migration? **Nia:** The best test is a simple conversation. Ask your agent a question that requires it to remember something from a previous session . If it can pull that context, you know your `sessions` and `memory` migrated correctly. If it acts like it’s never met you before, something went wrong with the state directory transfer . **Miles:** That’s a great "vibe check." What if it remembers me but can't actually perform any tasks, like searching the web or using a specific model? **Nia:** That usually points back to the credentials. Check your logs with `openclaw logs --follow` . If you see errors like "No API key found for provider," then your `auth-profiles.json` or `secrets.json` didn't land in the right spot . On Windows, double-check that you don't have that weird "missing backslash" issue in your state directory path—`openclaw doctor` should have caught it, but the logs will confirm if it’s still looking in the wrong place . **Miles:** Is there anything else that might break even if I did everything perfectly? You mentioned earlier that some things are tied to the specific machine. **Nia:** Yeah, that’s a real thing. Certain OAuth callbacks or IP allowlists might be tied to your old machine’s hostname or IP address . So if you’ve moved to a new Windows 11 box entirely, you might need to jump into your LLM provider’s dashboard—like Anthropic or OpenAI—and make sure your new IP isn't being blocked . **Miles:** Good to know. So it’s not just about the files; it’s about the environment too. What about the gateway itself? How do I make sure it’s running efficiently on the new version? **Nia:** Keep an eye on the "Gateway Health" section in `openclaw doctor` . It’ll tell you if the service is running under the correct user and if there are any risky "open" settings in your DM policies that you might want to tighten up now that you’re on a fresh install . It’s also a good time to check if you’re on the right "channel"—you can use `openclaw update --channel dev` if you want the absolute bleeding-edge features, or stick to the stable release if you want to avoid doing this whole migration again next week . **Miles:** I think I’ll stick to the stable channel for now. One migration a day is plenty for me.
Chapter 8The Practical Playbook for Your Next Update
**Miles:** This has been incredibly helpful. I feel like I actually have a roadmap now. If we had to boil this down to a "cheat sheet" for someone about to hit that update button on Windows 11, what are the non-negotiables? **Nia:** Rule number one: You can back up while the gateway is running . Think of it like turning off the car before you change the oil. Use `openclaw gateway stop` and make sure it’s actually down . **Miles:** Got it. Stop the engine. Rule number two? **Nia:** Use the built-in tools. Don't just copy-paste folders and hope for the best. Run `openclaw backup create --verify` to get that timestamped, verified archive . It captures the four big ones: Config, Credentials, Sessions, and Workspaces . And keep that archive somewhere *off* your main drive—if your disk fails during the update, a backup on the same disk won't save you . **Miles:** Good call. Cloud storage or a USB stick it is. What’s the secret weapon for the installation phase? **Nia:** That would be `openclaw doctor` . Run it after the install, run it after you restore your files, and run it if anything feels "off" . It’s designed to handle the messy parts of Windows pathing and service migration so you don't have to . **Miles:** And if I get stuck? If I’m looking at a "No API key found" error even after running the doctor? **Nia:** Then you go to the logs. `openclaw logs` is your best friend . It’ll tell you exactly where the app is looking for those files. If it’s looking in `C:\Users\Username.openclaw` instead of `C:\Users\Username\.openclaw`, you know you’ve hit that path-concatenation bug and you might need to manually set your `OPENCLAW_STATE_DIR` environment variable to bridge the gap until the next patch . **Miles:** It’s all about having a plan. I feel way more confident now. It’s not just a "reinstall"—it’s an evolution of the system. **Nia:** Exactly. And once you’ve done it once, you can actually script it. You can set up a Windows Task Scheduler job to run that `openclaw backup create` command every night at 3 AM . That way, the next time a big update rolls around, you already have a library of verified archives waiting for you .
Chapter 9Reflections on a Seamless Migration
**Miles:** So, we’ve gone from "I’m scared to touch the update button" to "I have a nightly automated backup strategy." That’s a pretty big jump for one conversation. It’s funny how a little bit of technical clarity can turn a stressful chore into just another part of your workflow. **Nia:** It really is about trust, right? You’re putting a lot of "life" into these agents—memories, notes, conversation history. The `openclaw backup` command exists so that trust doesn’t have to end in tears if a disk fails or an update goes sideways . When you have a verified archive, you’re not just saving files; you’re saving the continuity of your agent’s "identity" . **Miles:** I love that idea—continuity of identity. It makes the tech feel a lot more human. Before we wrap up, what’s the one thing you think someone should do the moment they finish this episode? **Nia:** Honestly? Just run `openclaw info` . Don't even start the migration yet. Just see where your data lives. Knowing where your "state" is—and confirming it’s not in some weird path with a missing backslash—is the first step toward owning your setup instead of just using it . **Miles:** Knowledge is power, especially when it comes to your own file system. I’m going to go run that right now and see if my "test" agent is actually where I think it is. **Nia:** Good luck with the migration! It’s a great feeling when you finally boot up that latest version and everything—your history, your keys, your agent’s personality—is right where you left it. It’s like moving into a new house and finding all your furniture already perfectly arranged. **Miles:** Thanks for walking me through this. It’s been a blast. **Nia:** Anytime. To everyone out there getting their Windows 11 setups ready for the future of OpenClaw—you’ve got this. Take the backup, run the doctor, and enjoy the new features. Thanks for listening and diving into the "lobster way" with us today. Take a second to think about which part of your agent's memory would be the hardest to lose—and then go make sure it's backed up.
What people search for about How To Update Openclaw On Windows 11
When users look for ways to update OpenClaw on Windows 11, they are typically trying to figure out how to transition to the newest version safely. Common concerns include finding the hidden `.openclaw` directory, backing up agent memory, and using PowerShell or the native Windows Hub companion app to complete the installation.
A practical guide to How To Update Openclaw On Windows 11
Updating OpenClaw on Windows 11 requires careful handling of your local agent data to ensure a smooth transition. This guide walks you through the process of locating your files, backing up your data, and performing the update. **Locating the .openclaw Folder** By default, OpenClaw stores its state directory in your user profile. On Windows 11, this is typically located at `~/.openclaw` (which resolves to `C:\Users\YourUsername\.openclaw`). This folder contains your agent workspaces, sandboxes, and configuration files. **Files to Back Up** Before uninstalling or updating, it is crucial to back up specific files to protect your AI assistant's state. Ensure you create a copy of your: - Profile and settings - Agents and their session history - API keys and bot tokens - Agent memory and workspaces **Basic PowerShell Backup** You can use basic PowerShell commands to create a backup archive of your OpenClaw directory. Open PowerShell and run a command similar to: `Copy-Item -Path "$HOME\.openclaw" -Destination "$HOME\Desktop\openclaw_backup" -Recurse` *Note: Depending on your system's execution policies, you may need to adjust PowerShell permissions or run as an administrator, though standard copy commands usually execute without issue.* **Uninstall, Reinstall, and Verification** 1. **Uninstall**: Remove the current OpenClaw Companion app from your Windows 11 system via the Settings > Apps menu. 2. **Reinstall**: Download the latest stable Hub installer for Windows. You can also use the PowerShell CLI installer or a WSL2 Gateway if preferred. 3. **Restore**: If needed, move your backed-up files back into the `~/.openclaw` directory. 4. **Verification**: Launch the OpenClaw Companion from the Start menu or system tray. Verify your agent's memory, API keys, and workspaces are intact and functioning correctly.
Continue learning about How To Update Openclaw On Windows 11
Explore more topics related to managing AI agents, troubleshooting Windows CLI environments, and maintaining local machine learning workspaces.
Best quote from Migrating OpenClaw: How to Protect Your Agent’s Memory and Data
Think of the state directory as the 'nervous system'—it’s got your config, your auth tokens, and your session history. If you don't back that up, your agent basically wakes up with total amnesia—no history, no keys, no memories.
Knowledge sources
Updating – OpenClaw - Open Source AI Coding Assistant
Migration Guide – OpenClaw - Open Source AI Coding Assistant
[Bug]: Bug]: [Windows] Agent/auth lookup uses wrong state directory path (missing backslash between username and .openclaw) Agent/auth 查找使用错误的状态目录路径（用户名与 .openclaw 之间缺少反斜杠） · Issue #40563 · openclaw/openclaw
FAQ
You can update to the latest version by downloading the newest stable Hub installer for Windows, or by using the built-in update mechanism if your version supports it. Always back up your ~/.openclaw directory before initiating a major update or reinstallation.
Yes, OpenClaw has mechanisms to update itself. The Sparkle framework can update the companion app, which then automatically runs the openclaw update command upon relaunch, restarts its Gateway, and verifies system health.
To reinstall OpenClaw on Windows, first back up your agent memory and API keys located in the ~/.openclaw folder. Then, uninstall the current application through Windows settings and download the latest Hub installer or use the PowerShell CLI installer to set it up again.
From Columbia University alumni built in San Francisco
"Instead of endless scrolling, I just hit play on BeFreed. It saves me so much time."
"I never knew where to start with nonfiction—BeFreed’s book lists turned into podcasts gave me a clear path."
"Perfect balance between learning and entertainment. Finished ‘Thinking, Fast and Slow’ on my commute this week."
"Crazy how much I learned while walking the dog. BeFreed = small habits → big gains."
"Reading used to feel like a chore. Now it’s just part of my lifestyle."
"Feels effortless compared to reading. I’ve finished 6 books this month already."
"BeFreed turned my guilty doomscrolling into something that feels productive and inspiring."
"BeFreed turned my commute into learning time. 20-min podcasts are perfect for finishing books I never had time for."
"BeFreed replaced my podcast queue. Imagine Spotify for books — that’s it. 🙌"
"It is great for me to learn something from the book without reading it."
"The themed book list podcasts help me connect ideas across authors—like a guided audio journey."
"Makes me feel smarter every time before going to work"
From Columbia University alumni built in San Francisco
"Instead of endless scrolling, I just hit play on BeFreed. It saves me so much time."
"I never knew where to start with nonfiction—BeFreed’s book lists turned into podcasts gave me a clear path."
"Perfect balance between learning and entertainment. Finished ‘Thinking, Fast and Slow’ on my commute this week."
"Crazy how much I learned while walking the dog. BeFreed = small habits → big gains."
"Reading used to feel like a chore. Now it’s just part of my lifestyle."
"Feels effortless compared to reading. I’ve finished 6 books this month already."
"BeFreed turned my guilty doomscrolling into something that feels productive and inspiring."
"BeFreed turned my commute into learning time. 20-min podcasts are perfect for finishing books I never had time for."
"BeFreed replaced my podcast queue. Imagine Spotify for books — that’s it. 🙌"
"It is great for me to learn something from the book without reading it."
"The themed book list podcasts help me connect ideas across authors—like a guided audio journey."
"Makes me feel smarter every time before going to work"
"Instead of endless scrolling, I just hit play on BeFreed. It saves me so much time."
"I never knew where to start with nonfiction—BeFreed’s book lists turned into podcasts gave me a clear path."
"Perfect balance between learning and entertainment. Finished ‘Thinking, Fast and Slow’ on my commute this week."
"Crazy how much I learned while walking the dog. BeFreed = small habits → big gains."
"Reading used to feel like a chore. Now it’s just part of my lifestyle."
"Feels effortless compared to reading. I’ve finished 6 books this month already."
"BeFreed turned my guilty doomscrolling into something that feels productive and inspiring."
"BeFreed turned my commute into learning time. 20-min podcasts are perfect for finishing books I never had time for."
"BeFreed replaced my podcast queue. Imagine Spotify for books — that’s it. 🙌"
"It is great for me to learn something from the book without reading it."
"The themed book list podcasts help me connect ideas across authors—like a guided audio journey."
"Makes me feel smarter every time before going to work"
"Instead of endless scrolling, I just hit play on BeFreed. It saves me so much time."
"I never knew where to start with nonfiction—BeFreed’s book lists turned into podcasts gave me a clear path."
"Perfect balance between learning and entertainment. Finished ‘Thinking, Fast and Slow’ on my commute this week."
"Crazy how much I learned while walking the dog. BeFreed = small habits → big gains."
"Reading used to feel like a chore. Now it’s just part of my lifestyle."
"Feels effortless compared to reading. I’ve finished 6 books this month already."
"BeFreed turned my guilty doomscrolling into something that feels productive and inspiring."
"BeFreed turned my commute into learning time. 20-min podcasts are perfect for finishing books I never had time for."
"BeFreed replaced my podcast queue. Imagine Spotify for books — that’s it. 🙌"
"It is great for me to learn something from the book without reading it."
"The themed book list podcasts help me connect ideas across authors—like a guided audio journey."
"Makes me feel smarter every time before going to work"
