From Cooking Video to Recipe

Modern AI models, a powerful desktop workflow, and maximum flexibility — locally or in the cloud.

Verbixa CookBook is an application for turning existing cooking information into structured cookbook entries. Source material can include cooking videos, audio recordings, spoken recipes, and existing recipe text. The focus is on faithfully reconstructing the information actually present in the source and making it permanently usable in a personal recipe library.

CookBook supports multiple input methods. These include local audio and video files, supported online sources such as YouTube, recipes dictated directly into the application, structured manual entry, and imported free-form text.

Yes. Verbixa can detect the language of the video, transcribe the spoken content, and—depending on the selected workflow—translate it. It then uses the cooking information actually contained in the source to create a structured cookbook entry.

No. The source language can be detected automatically. Foreign-language videos, audio recordings, or recipe texts can then be processed in the currently selected Verbixa content language.

The user interface and language selection currently support German, English, French, Spanish, Italian, Dutch, Polish, Czech, Greek, Russian, Ukrainian, Portuguese, Turkish, Hungarian, Thai, Japanese, Korean, and Chinese, among others. The underlying speech recognition system can also automatically detect additional languages.

Verbixa attempts to reconstruct ingredients, quantities, preparation steps, and other recipe information from the source and present them in a structured format. What matters, however, is which information is actually present or can be reconstructed reliably.

No—that is exactly what Verbixa CookBook is designed to avoid. Missing ingredients, quantities, temperatures, cooking times, serving sizes, or preparation steps are not simply invented based on general cooking knowledge. If relevant information is missing or uncertain, it can be omitted or flagged for review.

CookBook distinguishes between information that is explicitly supported, information that can be reconstructed reliably, and information that is merely plausible. Only sufficiently supported details should be included in the cookbook entry. Any practically relevant uncertainty can be flagged with an editorial review note.

Depending on the information available, an entry can include the recipe title, a brief description, servings, ingredients, preparation steps, variations, serving and plating suggestions, and editorial review notes. Unsupported or empty sections are not added artificially.

Yes. If a source primarily contains a cooking technique rather than a complete recipe, CookBook can turn it into an appropriately structured technique entry. If neither a recipe nor a relevant cooking technique can be reconstructed with sufficient confidence, the application should indicate this instead of inventing a recipe.

Yes. With “Dictate a Recipe,” you can record a recipe directly using a microphone. The application supports recording, pausing and resuming, stopping, and then using the recording for further processing.

Yes. Recipes passed down orally within families are one of the intended use cases. A recipe that has previously existed only as a spoken tradition can be recorded, structured, and then permanently stored in the recipe library.

Yes. Recipe text can either be entered manually in a structured format or pasted as complete free-form text. Suitable source material includes text from websites, PDFs, emails, chats, or notes. CookBook then attempts to extract the relevant recipe components.

Yes. For longer media files, you can specify a start and end point. An audio preview is also available, allowing you to process only the section that contains the actual recipe, for example.

Not necessarily. CookBook includes mechanisms designed to work with current YouTube access methods. However, individual videos may not be processable due to platform changes, access restrictions, sign-in requirements, or technical characteristics of the source. Therefore, the website should not claim that every YouTube video will work.

Yes. Recipes can be exported as DOCX files and then edited further, for example in Microsoft Word. In addition, library entries can be renamed, moved, and managed.

CookBook can generate recipe documents as PDF and DOCX files for use with Microsoft Word. A TXT version is also created. The PDF and DOCX files use the same recipe structure and content.

Optionally, additional source information can be appended to the recipe documents. This can include a cleaned-up translation of the transcript and/or the cleaned-up original transcript. These attachments are disabled by default.

CookBook manages generated recipes in its own library. You can create custom categories or subfolders and organize your recipes over the long term. The structure is not fixed and can be adapted to suit your personal recipe collection.

Yes. The library provides search and filtering options, including by keyword, category, language, and source or input channel. Information displayed can include the recipe name, category, language, and source.

Yes. Verbixa stores metadata about the origin of a recipe. It distinguishes, for example, between local files, online or YouTube sources, dictated recipes, manual entries, and imported free-form text. For YouTube sources, available channel information can also be retained.

Recipes created from the same original source can be linked and displayed as variations of a primary recipe. If a conflict occurs, you can choose to use an existing version, create a new variation, or assign a different name.

Speech recognition can run locally. This means the audio material does not necessarily need to be sent to an external speech recognition service for transcription alone.

Yes. On suitable hardware, local AI models can be used via Ollama. Availability depends in part on the system resources available.

Not every workflow can operate completely offline. Local speech recognition and local AI processing are possible, but accessing YouTube or using configured cloud-based AI services, for example, requires a network connection.

For local AI processing using properly configured local models, no cloud API key is required. If external AI services are used, the corresponding credentials or API keys may be required. CookBook supports setting up and validating these credentials.

On Windows, newly stored API keys are protected using Verbixa’s credential infrastructure. According to the documented implementation, they are stored using Windows DPAPI within the current user context.

Yes. CookBook is a standalone application and also part of the Verbixa Suite. Among other things, Verbixa Studio can be opened directly from CookBook, and existing recipe collections from Studio can be incorporated into the CookBook library.

Verbixa CookBook currently has a German and an English user interface, with additional language versions planned. The source language, content language, and language of the generated documents are handled independently of the interface language.

Yes. CookBook has its own trial and license management. Under the model currently planned for your website, the full version can be tested free of charge for 14 days. After that, an appropriate license is required to create new recipes; existing library functions can be handled separately. The 14-day period comes from your current sales model, while the technical feature description itself only documents support for a trial-version state.

Under the current sales model, CookBook is unlocked with a one-time payment. There are no monthly Verbixa fees. Any costs for external AI services are separate and may apply if the user configures such services.

Windows 10 and Windows 11, 64-bit.

• Verbixa Homepage