Free: 30 Easy Vegan Recipes for Notion
A free Notion recipe database pre-loaded with 30 genuinely easy vegan recipes — already tagged by meal type, cook time, and main ingredient so you can filter and cook on day one.
Most free recipe templates hand you an empty database and a pat on the back. That's the hard part left undone — a structure is useless until it's full, and filling it is exactly the work people don't have time for. This one ships with 30 easy vegan recipes already in it, already tagged, ready to filter and cook.
Here's what's inside, why it's structured the way it is, and how to use it.
What you get
A single Notion database, Recipes, pre-loaded with 30 plant-based recipes. Every one is:
- Genuinely easy — short ingredient lists, common pantry staples, minimal technique. No "easy" recipe that secretly needs three pans and a food processor.
- Pre-tagged so the filters work the moment you duplicate it.
- Honest on time — the cook-time number is real, not the optimistic version.
The recipes span the week: breakfasts (overnight oats, tofu scramble), fast lunches (chickpea salad, grain bowls), weeknight dinners (one-pot pastas, curries, stir-fries), and a few snacks and simple desserts.
How it's structured
Each recipe is a row with these properties already filled in:
- Meal type — breakfast, lunch, dinner, snack, dessert
- Cook time (minutes) — so you can sort fastest-first
- Effort — low / medium
- Main ingredient — tofu, lentils, chickpeas, pasta, etc.
Because the tagging is done, the views actually do something on day one:
- A Weeknight view filtered to low-effort recipes under 30 minutes
- A board grouped by main ingredient so you can cook from what's in the fridge
- A by-meal-type view for when you specifically need a breakfast or a lunch
That's the whole point of starting with a populated database — you experience the payoff (filtering down to "vegan, under 30 minutes, uses chickpeas") immediately, instead of staring at an empty table wondering where to begin.
A sample of what's inside
To give you a sense of the range, here's a slice of the 30:
- Breakfasts: overnight oats (no cooking at all), a 10-minute tofu scramble, banana-oat pancakes
- Fast lunches: smashed-chickpea sandwich filling, a peanut-noodle bowl, a lemony lentil-and-greens salad
- Weeknight dinners: one-pot tomato pasta, red lentil dahl, a soy-ginger tofu stir-fry, black bean tacos, a coconut chickpea curry
- Snacks and sweets: hummus with whatever's in the fridge, energy balls, two-ingredient chocolate mousse
None of them need special equipment or hard-to-find ingredients. If you can boil pasta and use an oven, you can cook every recipe in the database. That's the deliberate ceiling — these are the recipes that survive a tired Tuesday, which is exactly when most plant-based plans fall apart.
How to use it
- Duplicate it into your own Notion workspace (Duplicate button, top right).
- Open the Weeknight view and pick two or three dinners for the week.
- Cook one tonight. The recipes are designed so you can.
- Add your own as you go — keep the same four properties and your new recipes slot straight into the existing views.
The recipes you add inherit all the filtering for free, because the structure is already there. That's the real gift: not the 30 recipes, but a working system seeded well enough that adding to it is effortless.
Why 30 and why "easy"
Thirty is enough to cover a month of dinners without repeating, and few enough that every recipe is one you'd actually make. Bigger free packs sound generous but bury the good recipes under filler you'll never cook.
And "easy" is the constraint that matters most when you're starting out or busy. The recipes that change how you eat aren't the impressive ones — they're the ones simple enough that you reach for them on a tired Tuesday. This database is built entirely from those.
Make it yours
The template is a starting point, not a finished thing. A few quick ways to adapt it once it's in your workspace:
- Add a
Statusproperty (want to try / favorite / nope) so the database starts reflecting your taste, not just mine. Your favorites view becomes your real go-to list within a couple of weeks. - Tag a
Servingsnumber if you cook for more than one — it makes scaling and grocery math easier later. - Drop in your own substitutions. If you always swap tofu for chickpeas, note it on the page. The database becomes a record of how you cook, which is far more useful than any generic recipe site.
None of this is required. The template works untouched. But the people who get the most from it are the ones who let it accumulate their own preferences over time, so that six months in it's a personalized cookbook rather than a borrowed one.
Where to take it next
Once the recipe database is part of your week, the natural next steps are a meal planner that links to it and a grocery list that builds from your plan — turning this library into a full plan-shop-cook loop. But don't rush there. Use the 30 recipes for two weeks first. A recipe library you actually open beats a three-database system you admire and abandon.
Grab it free, duplicate it, and cook something tonight.