Your Recipes in Sync Without the Lock-in

You want your recipes on your phone and your desktop. You want them backed up. But you don't want to hand your entire recipe collection to a company that might disappear, change their pricing, or get acquired tomorrow.

That's the tension most recipe apps never solve. You either sync to the cloud and lose control, or you keep them local and manage syncing manually.

Cook does both.

How Cook Cloud works

Cook Cloud syncs your recipes across every device — phone, desktop, tablet. Sign in once, and your recipes are there. Add a new one on your phone, and it's on your desktop within seconds.

But here's the key difference: your recipes are stored as plain-text .cook files. Not in a proprietary database. Not locked behind Cook's servers. Your actual files stay yours.

The right tool for the job

Cook Editor on desktop is where you write, organize, and refine your recipes. Scale them up, tweak instructions, build your collection. The mobile app is built for the kitchen — cooking mode, timers, shopping lists grouped by aisle. Two tools, each doing what it does best.

The Sync Agent and folder sync

Want more flexibility? The Sync Agent syncs your recipes through Cook Cloud, but the mobile app can also read recipes directly from any folder — Dropbox, Nextcloud, your own server. Point the app at a folder, and it reads your recipes from there. You stay in control of where your data lives.

Why this matters

Your recipes are plain-text files you can edit anywhere, back up however you want, and move anytime. If you ever leave Cook, they come with you — same files, zero conversion needed.

Next steps

Sign up for Cook Cloud to sync your collection, or read the Sync Agent guide to keep a local folder in sync your way.