About Forkcetera

Why I built this

I kept losing recipes. I’d save a reel and never find it again, screenshot something and lose it in my camera roll, or jot down a note I couldn’t make sense of later. And the times I did track one down, I’d be scrubbing a video back to catch a step, or scrolling past someone’s holiday to get to the ingredients.

I wanted one place where the recipe just sits there, ready to cook. So I built it. Give Forkcetera a link, a photo of a cookbook page, or some text, and it saves the recipe clean — nothing to comment on, no website to chase, no video to rewatch.

Who it's for

I built it for me and my girlfriend. We cook most nights, and the recipes we actually use were scattered across Instagram saves, screenshots and half-written notes we could never find again. Now they live in one cookbook, all of it searchable, ready when we’re standing in the kitchen. If your recipes are scattered the same way, it’s for you too.

About me

I’m James Wallis, a software engineer who cooks a lot. I build Forkcetera in my own kitchen. It started as something just for us, but I’d love for more people to cook from it. If something’s missing, broken, or just annoying, tell me — I read every message.

Find me at wallis.dev or on GitHub.