Repository navigation
docs: new file formats GA — drop beta labels, document the 50k billing floor - #481
Conversation
…g floor Ten beta formats (xlsm, zip/SCORM, vtt, yaml, properties, strings, md, resx, odt, rtf) plus jpeg/png image translation are generally available as of 2026-11-02 (TW-2713). - Strip '(currently in beta)' from the format lists in openapi.yaml, openapi.json, and the document-translations gotcha headers. - Billing minimums: document-like formats (docx, doc, pptx, xlsx, xlsm, pdf, odt, rtf, SCORM zip, jpeg/png, idml, mif) bill a 50,000-character minimum; text-like formats bill exact characters. Replaces the old 'beta formats are not billed' claim in document-translations, translate-documents-quickstart, and usage-limits. - Changelog entry for November 2; about.mdx format list updated.
Preview approval requiredThis pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit |
| </Update> | ||
|
|
||
| <Update label="October 2026"> | ||
| ## November 2 - New File Formats Generally Available |
There was a problem hiding this comment.
This entry is inside <Update label="October 2026">, but a <Update label="November 2026"> block already exists above (it holds "November 2 - Custom Instructions for Document Translation"). Please move this entry into the November block so the changelog label and RSS grouping are correct.
There was a problem hiding this comment.
Good catch — moved the Nov 2 GA entry into the November 2026 <Update> block (it now sits after the Custom Instructions entry). Fixed in 855fc8d.
|
|
||
| <Update label="October 2026"> | ||
| ## November 2 - New File Formats Generally Available | ||
| - Ten formats introduced in beta on September 29 — `xlsm` (macro-enabled Excel), `zip` (SCORM e-learning packages), `vtt` (WebVTT subtitles), `yaml` / `yml`, `properties` (Java properties), `strings` (iOS/macOS strings), `md` / `markdown`, `resx` (.NET resources), `odt` (OpenDocument Text), and `rtf` (Rich Text Format) — plus `jpeg` / `png` image translation, are now generally available in [`POST /v2/document`](/api-reference/document/upload-and-translate-a-document). They are no longer marked beta and are now billed like other formats. |
There was a problem hiding this comment.
"are now billed like other formats" is the sentence beta users will read as the price change, and the next bullet then gives two different rules (50k floor vs exact count). Suggest saying it directly, e.g. "During beta these formats were not billed. They now count toward your character usage, with the billing rules below."
There was a problem hiding this comment.
Agreed — reworded to: "During beta these formats were not billed. They now count toward your character usage, with the billing rules below." Fixed in 855fc8d.
|
|
||
| *DeepL supports XLIFF versions 1.2, 2.0, and 2.1 (2.1 shares the 2.0 core namespace).<br /> | ||
| **Currently in Beta. During the Beta phase, characters translated in these file formats are not billed and not counted against your character threshold. | ||
| Document-like formats (`.docx`, `.doc`, `.pptx`, `.xlsx`, `.xlsm`, `.pdf`, `.odt`, `.rtf`, SCORM `.zip`, `.jpeg`/`.png`, `.idml`, `.mif`) are billed a minimum of 50,000 characters per document; text-like formats are billed for their exact character count. See [Document translations](/docs/best-practices/document-translations#billing-minimums). |
There was a problem hiding this comment.
Two things here:
- The old
**Currently in Betafootnote carried the**marker. It is gone now, but ten table rows above still end in\*\*(YAML, Properties, Strings, Markdown, WebVTT, SCORM, RESX, ODT, RTF, Images), so they point at nothing. Please remove those markers. - This sentence now sits directly under the XLIFF
*footnote and reads as part of it. Make it its own paragraph, or a<Note>.
There was a problem hiding this comment.
Both fixed in 855fc8d: removed the orphaned \*\* markers from all ten table rows (XLIFF keeps its single \* footnote), and the billing sentence is now its own paragraph after the XLIFF footnote.
|
|
||
| ### Billing minimums | ||
| Every submitted document of type `.pptx`, `.docx`, `.doc`, `.xlsx`, or `.pdf` is billed a minimum of 50,000 characters on DeepL API plans, no matter how many characters the document contains. Formats currently in beta are not billed and are not subject to this minimum. | ||
| Documents of type `.docx`, `.doc`, `.pptx`, `.xlsx`, `.xlsm`, `.pdf`, `.odt`, `.rtf`, SCORM (`.zip`), `.jpeg`/`.png`, `.idml`, and `.mif` are billed a minimum of 50,000 characters on DeepL API plans, no matter how many characters the document contains. Text-like formats (`.txt`, `.html`, `.xml`, `.json`, `.yaml`/`.yml`, `.properties`, `.strings`, `.md`, `.dita`, `.xlf`/`.xliff`, `.srt`, `.vtt`, `.resx`) are billed for their exact character count with no minimum. |
There was a problem hiding this comment.
The two lists here (and the same lists in the changelog, usage-limits.mdx and the quickstart warning) don't match the supported-formats list:
.docis listed for billing but is not a supported format in the openapi format list..htm,.jpgand.markdownare supported but missing from the billing lists.
Since each list reads as a closed set, please make them consistent (or add a "and their alternate extensions" note).
There was a problem hiding this comment.
Fixed in 855fc8d — all four billing lists (this section, changelog, usage-limits, quickstart warning) now match the supported-format list: added .jpg, .htm/.html, and .md/.markdown; the Images row is now .jpeg/.jpg/.png. Kept .doc since it's accepted by the API (Word legacy) even though it's not a separate bullet in the openapi list — happy to drop it if you'd rather the list mirror the bullets exactly.
…st consistency - Move the Nov 2 GA entry into the November 2026 <Update> block. - State the billing change directly: beta formats were not billed, now they count toward character usage with the rules below. - Remove orphaned ** markers from the usage-limits table rows (footnote deleted) and give the billing sentence its own paragraph. - Align billing lists with the supported-format list: add .jpg, .htm, .markdown; Images row now .jpeg/.jpg/.png.
kabraham13
left a comment
There was a problem hiding this comment.
Checked 855fc8d against the earlier comments: changelog entry is in the November block, orphaned footnote markers are gone, the billing sentence is explicit, and the format lists now include .jpg/.htm/.markdown. Keeping .doc is fine since the usage-limits table lists Word as .docx / .doc.
What
Ten formats introduced in beta on Sept 29 (
xlsm,zip/SCORM,vtt,yaml/yml,properties,strings,md/markdown,resx,odt,rtf) plusjpeg/pngimage translation are generally available as of 2026-11-02 (TW-2713). This PR:(currently in beta)from the format lists inopenapi.yaml,openapi.json, and the format-gotcha headers indocument-translations.mdx(54 labels)..docx,.doc,.pptx,.xlsx,.xlsm,.pdf,.odt,.rtf, SCORM.zip,.jpeg/.png,.idml,.mif) → 50,000-character minimum per document..txt,.html,.xml,.json,.yaml/.yml,.properties,.strings,.md,.dita,.xlf/.xliff,.srt,.vtt,.resx) → exact character count, no minimum.document-translations.mdx(Billing minimums),translate-documents-quickstart.mdx, andusage-limits.mdx.about.mdx.Verification
Jira: TW-2713