AI Meeting Note Tools That Support Multiple Languages

Tested prompts for ai meeting notes in multiple languages compared across 5 leading AI models.

BEST BY JUDGE SCORE Claude Haiku 4.5 7/10

The prompt we tested

You are a multilingual meeting notes assistant. Follow these instructions exactly:

Auto-detect the source language of the transcript and produce notes in that language plus any additional target languages specified by the user (default: English and Spanish if none specified). Use clear Markdown headings per language (e.g., ## English, ## Español), keep each section concise with bullet points, and preserve names, numbers, and technical terms exactly as spoken without translating them.

Meeting transcript or recording notes:
Transcript from today's product sync (mixed English and German): Anna sagte, dass das neue Dashboard bis zum 15. November fertig sein muss. Marcus agreed to handle the API integration and will send a draft spec by Friday. We still need to decide whether to support Japanese localization in v2. Target languages: English, German, Japanese.

Produce structured meeting notes in the detected source language AND translated into the requested target languages. For each language version, include: Summary, Key Decisions, Action Items (with owner and due date if mentioned), and Open Questions.

Model comparison

ModelQualityCostLatencyTokens
Claude Opus 4.7 7 $0.0509 7.9s 351 / 608
Claude Haiku 4.5 7 $0.0028 4.2s 230 / 508
GPT-5.4 4 $0.0084 7.0s 210 / 528
Gemini 2.5 Pro 2 $0.0007 16.8s 212 / 87
Grok 4.1 Fast Reasoning 7 $0.0002 7.3s 359 / 310

Outputs

Claude Opus 4.7 7/10
## English

**Summary**
- Product sync covering dashboard delivery, API integration ownership, and v2 localization scope.

**Key Decisions**
- The new dashboard must be completed by 15. November.
- Marcus will own the API integration.

**Action Items**
- Anna: Deliver the new Dashboard — due 15. November.
- Marcus: Send a draft spec for the API integration — due Friday.

**Open Questions**
- Should we support Japanese localization in v2?

---

## Deutsch

**Zusammenfassung**
- Product Sync zu Dashboard-Lieferung, Verantwortung für die API-Integration und Lokalisierungsumfang in v2.

**Wichtige Entscheidungen**
- Das neue Dashboard muss bis zum 15. November fertig sein.
- Marcus übernimmt die API-Integration.

**Aufgaben**
- Anna: Neues Dashboard liefern — fällig am 15. November.
- Marcus: Entwurf der Spec für die API-Integration senden — fällig Freitag.

**Offene Fragen**
- Sollen wir Japanese localization in v2 unterstützen?

---

## 日本語

**サマリー**
- Dashboardの納期、API integrationの担当、v2でのローカライズ範囲についてのproduct sync。

**主な決定事項**
- 新しいDashboardは15. Novemberまでに完成させる必要がある。
- MarcusがAPI integrationを担当する。

**アクションアイテム**
- Anna: 新しいDashboardの提供 — 期限: 15. November。
- Marcus: API integrationのdraft specを送付 — 期限: Friday。

**未解決の質問**
- v2でJapanese localizationをサポートするかどうか?
Judge notes: The Japanese section inconsistently mixes untranslated English/German terms (e.g., "15. November," "Friday," "Dashboard," "draft spec") where natural Japanese equivalents or at least consistent localization conventions should have been applied, and the German section similarly leaves "Japanese localization" untranslated when "japanische Lokalisierung" would be appropriate.
Claude Haiku 4.5 7/10
# Meeting Notes - Product Sync

## English

### Summary
The team discussed dashboard completion requirements, API integration responsibilities, and localization support for the upcoming product version.

### Key Decisions
- Dashboard must be completed by November 15
- Marcus assigned to handle API integration

### Action Items
- **Marcus**: Send API integration draft spec by Friday
- **Team**: Decide on Japanese localization support for v2

### Open Questions
- Will v2 support Japanese localization?

---

## Deutsch

### Zusammenfassung
Das Team diskutierte die Fertigstellungsanforderungen des Dashboards, API-Integrations-Verantwortlichkeiten und die Unterstützung der Lokalisierung für die kommende Produktversion.

### Wichtigste Entscheidungen
- Dashboard muss bis zum 15. November fertig sein
- Marcus ist für die API-Integration zuständig

### Maßnahmenpunkte
- **Marcus**: Entwurfsspezifikation für API-Integration bis Freitag senden
- **Team**: Entscheidung über Unterstützung der japanischen Lokalisierung für v2 treffen

### Offene Fragen
- Wird v2 die japanische Lokalisierung unterstützen?

---

## 日本語

### 要約
チームはダッシュボード完成要件、API統合の責任分担、および次期製品バージョンのローカライゼーション対応について議論した。

### 主要な決定事項
- ダッシュボードは11月15日までに完成する必要がある
- Marcus が API 統合を担当する

### アクションアイテム
- **Marcus**: 金曜日までに API 統合のドラフト仕様書を送付する
- **チーム**: v2 の日本語ローカライゼーション対応について決定する

### 未解決の質問
- v2 は日本語ローカライゼーションに対応するか?
Judge notes: The output is clean and well-structured, but it misses the instruction to auto-detect and include the source language as a distinct section (the transcript was mixed English/German, neither of which was surfaced as a detected source language note), and "Maßnahmenpunkte" is an awkward/non-standard German term for "Action Items" (the more natural term would be "Aufgaben" or "Aktionspunkte").
GPT-5.4 4/10
## English

- **Summary**
  - Anna said that the new Dashboard must be finished by **15. November**.
  - Marcus agreed to handle the **API integration** and will send a draft spec by **Friday**.
  - The team still needs to decide whether to support **Japanese localization** in **v2**.

- **Key Decisions**
  - **Marcus** will handle the **API integration**.
  - A draft spec will be sent by **Friday**.

- **Action Items**
  - **Marcus** — handle the **API integration**.
  - **Marcus** — send draft spec by **Friday**.
  - Team — complete the new **Dashboard** by **15. November**.

- **Open Questions**
  - Whether to support **Japanese localization** in **v2**.

## Deutsch

- **Zusammenfassung**
  - Anna sagte, dass das neue **Dashboard** bis zum **15. November** fertig sein muss.
  - Marcus stimmte zu, die **API integration** zu übernehmen, und wird bis **Friday** einen draft spec senden.
  - Es muss noch entschieden werden, ob **Japanese localization** in **v2** unterstützt werden soll.

- **Wichtige Entscheidungen**
  - **Marcus** übernimmt die **API integration**.
  - Ein draft spec wird bis **Friday** gesendet.

- **Aktionspunkte**
  - **Marcus** — übernimmt die **API integration**.
  - **Marcus** — sendet draft spec bis **Friday**.
  - Team — das neue **Dashboard** bis zum **15. November** fertigstellen.

- **Offene Fragen**
  - Ob **Japanese localization** in **v2** unterstützt werden soll.

## 日本語

- **Summary**
  - Anna said the new **Dashboard** must be completed by **15. November**.
  - Marcus agreed to handle the **API integration** and will send a draft spec by **Friday**.
  - The team still needs to decide whether to support **Japanese localization** in **v2**.

- **Key Decisions**
  - **Marcus** will handle the **API integration**.
  - A draft spec will be sent by **Friday**.

- **Action Items**
  - **Marcus** — handle the **API integration**.
  - **Marcus** — send draft spec by **Friday**.
  - Team — complete the new **Dashboard** by **15. November**.

- **Open Questions**
  - Whether to support **Japanese localization** in **v2**.
Judge notes: The Japanese section is not translated into Japanese at all — it's identical to the English section, which is a critical failure for the core multilingual task; additionally, the German section leaves "Friday" and "draft spec" untranslated when German equivalents exist.
Gemini 2.5 Pro 2/10
Of course. Here are the meeting notes from the product sync, formatted as requested. The source language was detected as a mix of German and English.

## English

### Summary
The team reviewed the timeline for the new dashboard, assigning the API integration task to Marcus. A decision regarding support for Japanese localization in the next version is still pending.

### Key Decisions
*   The new Dashboard must be completed by the 1
Judge notes: The output is severely truncated mid-sentence, delivering only a fragment of one language section out of the three required (English, German, Japanese), making it essentially unusable.
Grok 4.1 Fast Reasoning 7/10
## English

### Summary
- Product sync meeting: Discussion on new Dashboard deadline, API integration, and potential Japanese localization for v2.

### Key Decisions
- Marcus to handle API integration.

### Action Items
- Anna: Ensure new Dashboard is ready by 15. November (deadline stated).
- Marcus: Handle API integration and send draft spec by Friday.

### Open Questions
- Whether to support Japanese localization in v2.

## Deutsch

### Zusammenfassung
- Product-Sync-Meeting: Diskussion über Frist für neues Dashboard, API-Integration und mögliche Japanese Localization für v2.

### Wichtige Entscheidungen
- Marcus übernimmt die API-Integration.

### Aufgaben
- Anna: Neues Dashboard bis 15. November fertigstellen (Frist genannt).
- Marcus: API-Integration übernehmen und Draft-Spec bis Freitag senden.

### Offene Fragen
- Ob Japanese Localization in v2 unterstützt werden soll.

## 日本語

### 要約
- 製品同期ミーティング:新しい Dashboard の期限、API 統合、および v2 での Japanese localization の可能性についての議論。

### 主要決定事項
- Marcus が API 統合を担当。

### アクションアイテム
- Anna:新しい Dashboard を 15. November までに完了(期限が述べられた)。
- Marcus:API 統合を担当し、金曜日までに draft spec を送信。

### 未解決質問
- v2 で Japanese localization をサポートするか。
Judge notes: The output correctly follows the structure and preserves technical terms, but the Japanese section inconsistently mixes English terms like "Japanese localization" and "draft spec" where natural Japanese equivalents (日本語ローカライゼーション, ドラフト仕様書) would be more appropriate, and "15. November" in the Japanese section is oddly German-formatted rather than the standard Japanese date format (11月15日).

Related queries