NiaDocs
Latest
Menu

Nia documentation · Latest

Recipes

Build private cookbooks, assign ingredient quantities to steps, use cooking mode, import drafts and send ingredients to Shopping.

Recipes is part of the Nia V4. Enable it under Modules in your account settings, then choose Recipes in the sidebar’s module selector. Cookbooks do not use Tasks workspaces.

Cookbooks and recipe cards

Choose Create cookbook, give it a name and select its appearance and ownership. Open a cookbook to browse its recipe cards. Cards show an image or placeholder, title, a short description and available recipe details.

Search matches recipe titles, tags and ingredient names. Tag filters combine: selecting two tags shows recipes with both. You can sort by name, newest or total time. There is no separate category hierarchy.

Cookbooks can be personally owned, directly shared or owned by a household. Recipes inherit their cookbook’s access; an individual recipe does not have a separate sharing permission.

There is no public recipe discovery or cookbook archive workflow in this version.

Write a recipe

Open the add action in a cookbook, or choose the edit action in an existing recipe.

  1. Enter a title and optional description.
  2. Set the base servings and optional preparation and cooking times.
  3. Add a title image and any manual tags you want.
  4. Create ingredient groups, then add ingredients and quantities.
  5. Add preparation steps, with an optional heading and separate description for each.
  6. Save the recipe.

The base servings describe the quantities you enter in the editor. Changing portions in reading or cooking mode scales the display; it does not rewrite those base quantities.

Ingredients and groups

Use groups when ingredients belong to separate components, for example Dough and Filling. Click an ingredient to expand its fields, and click it again to close them. New ingredients can be named immediately; opening an existing ingredient does not automatically focus its name field.

Give each ingredient a name and either a numeric quantity with an optional unit or a free-text quantity such as “to taste”. Notes can describe preparation details. Known units use the same normalization as Shopping; unknown units stay literal.

Reorder ingredients, groups and steps with their move controls. The trash action deletes the corresponding entry. Deleting an ingredient also removes its step assignments.

Title images

Use the image placeholder next to the title to select an image. Activate an existing image to replace or remove it. Supported raster images are resized and normalized; the original image metadata is removed.

Title images are private recipe data, stored with the recipe in the server database. They follow cookbook permissions and do not use the Tasks attachment allowance. A shared image remains protected even if someone knows its URL.

Portions and practical quantities

The same minus/plus portions control is used in reading mode, cooking mode and the Shopping transfer dialog. Every calculation starts from the original recipe amounts.

For known mass and volume units, the display avoids long decimal tails:

  • amounts of 10 or more use whole units;
  • amounts from 0.5 to under 10 use half-unit steps;
  • smaller amounts retain the precision needed to avoid losing small quantities;
  • fractional larger units may use a smaller unit, such as 250 ml instead of 0.25 l.

Counts, spoon measures and unknown units keep their values rather than being rounded like metric weights. Common fractions use readable digits such as 1/4, 1/2 and 1 1/2. Free-text quantities are not mathematically scaled.

For example, scaling 250 ml from six servings to two displays 83 ml. Scaling one packet to one quarter keeps 1/4 of a packet. These are display rules; original amounts are retained for calculations and combining purchases.

Assign ingredients to steps

Under a step, expand Assign ingredients and select ingredients already entered in this recipe. With several populated groups, expand the groups you need. A single populated group is shown directly.

A selected ingredient uses its full recipe amount by default. Expand its amount controls to enter:

  • a numeric amount for that step, in the ingredient’s existing unit; or
  • a supported free-text amount, such as “zest and half the juice”.

Use Use full amount to remove the override. Numeric step amounts must be positive and no greater than that ingredient’s total.

For example, if the recipe contains 200 g flour and uses half for a dough and half later, assign 100 g to each relevant step. Changing portions scales both the totals and these step amounts.

Assignments make quantities visible while reading or cooking. They are not an automatically enforced consumption ledger: linking an ingredient in two steps does not subtract it from stock, and Nia does not check that all authored step amounts add up to its total. A later step working with prepared dough need not repeat all raw dough ingredients.

An unresolved imported assignment can show the ingredient followed by its recipe total in parentheses. That total is context, not a claim that the whole amount is used in the current step. Review unclear splits yourself.

Step assignments never increase the Shopping total. Each selected source ingredient is purchased once, regardless of how often it is referenced by steps.

Read and cook

Open a card for the reading view, which brings together ingredients, portions and preparation. Ingredient checkboxes help you keep track while preparing.

Switch to Cooking mode to show one step with its assigned ingredients and scaled amounts. The step content scrolls within its area; Previous step and Next step stay in a fixed footer. The compact portions control remains available.

Use Reading mode to leave cooking. The back action exits cooking before leaving the recipe. Editing and Shopping actions are available in reading mode.

Import a draft

  1. Choose Import recipe in the cookbook.
  2. Keep Link selected and enter a publicly accessible recipe URL.
  3. Choose whether to include its image.
  4. Select Create preview.
  5. Review and edit the draft, then save it.

URL import uses recipe-scrapers and structured recipe data; it does not call an LLM. It supports many websites and languages, but cannot import every page or bypass a login. Your client must reach your server, and the server must reach the source website.

The preview is unsaved. Review the servings, units, ingredient groups, step descriptions and source information. Source sites do not always supply all fields; imported groups and amounts depend on the available data. URL parsing does not infer ingredient quantities for each step.

From text or with BrainDump

The Text import mode and Revise with BrainDump action use the optional BrainDump configuration. They are available only when BrainDump is enabled globally and for your account, with a configured LLM. Recipe text workflows do not need a microphone recording.

Paste the recipe text to create a draft, or refine an existing unsaved draft. BrainDump can structure headings, clean promotional descriptions, fill unnamed ingredient groups and assign ingredients to steps. It can derive step amounts when instructions support them; ambiguous splits should remain unresolved.

Review generated amounts and assignments. BrainDump is not a verified recipe-consumption calculator. Concrete review findings appear beside the relevant step where available. If a provider request fails, your current draft stays available for manual editing.

Refinement protects manual ingredient selections and amount edits. Images are not sent to the model. Recipe text is sent to the configured provider, so its privacy and retention policy matter.

Send ingredients to Shopping

  1. In reading mode, choose Add to shopping list.
  2. Set portions and choose an editable shopping list.
  3. Select the products you need; the checklist is also the quantity preview.
  4. Optionally expand Section and store for common destinations.
  5. Open a product’s Details and selection to review source rows and adjust its destination. When equivalent entries have different notes, choose whether to combine them or keep them separate.
  6. Confirm the transfer.

Compatible numeric ingredients with the same name and destination combine by default across groups. For example, 250 g flour for dough and 100 g for dusting become 350 g. Compatible metric units can be converted. Notes are retained. When equivalent entries have different notes, Keep separate preserves those source rows and lets you assign them different destinations. Identical entries with the same notes are already consolidated and do not offer that choice.

Incompatible units, different destinations and free or unspecified amounts remain separate. Nia does not use synonyms to combine different product names. Step links do not contribute additional quantities.

A combined product has one destination editor. Common destination choices apply unless you make a product-specific choice. Memory can fill the list, section or stores when reliable, with sparkle badges marking remembered fields. Deliberately changed destinations are learned for later item entry and transfers.

The server can merge quantities into matching open Shopping items with compatible units, notes and destinations. Purchased items are left alone. Transferred content follows the Shopping list’s permissions: someone who can read the list can read the copied item even without access to its source cookbook.

Offline and conflicts

Previously synchronized cookbooks, recipes and cached images can be used offline. Supported edits and ingredient transfers are queued. An image not already cached may need a connection before it can be displayed.

A queued transfer does not immediately pretend to have merged Shopping items. It waits for server confirmation. A changed source recipe, invalid destination or revoked access can require you to review a blocked transfer. Do not repeatedly submit new transfers because one is waiting.

Removing a pending transfer stops local retry, but cannot undo an operation the server may already have accepted. A cookbook with a dependent transfer cannot be deleted until that transfer is settled or removed.

Concurrent recipe edits can require an explicit choice between the local draft and the server version. Review the conflict instead of assuming the last local save silently wins.

URL import and BrainDump requests require a connection; they are not queued as offline imports. Invitations and ownership changes also need the server.