Payload Crowdin Sync
Nested Payload documents reorganised into compact HTML and JSON for Crowdin translators.
Nested Payload documents, including blocks embedded in Lexical rich text, become HTML and JSON in Crowdin. File count stays low: one fields.json, one HTML file per rich text field, and a small folder per Lexical block.
Numbers, selects, dates, uploads, relationships, and fields you exclude stay in Payload. When translations are ready, they are written back into the same nested structure.
Few files per document
Each document becomes one fields.json plus an HTML file per rich text field. Nested Lexical blocks get their own small folders. Translators open a folder per page, not a file per field.
Only translatable strings
Numbers, selects, dates, uploads and relationships stay in Payload. Exclude slugs or other generated text. Translators never see editor state or field IDs.
Any nesting, including Lexical blocks
Groups, arrays, blocks, tabs, collapsibles and rows are walked. Blocks embedded in Lexical rich text are extracted and translated as their own small documents.
Rich text as HTML
Slate and Lexical fields become HTML that translators can edit in Crowdin, including uploads, relationships and tables. The plugin converts them back to editor state on the way in.
Uploads on save
Localized fields in collections and globals are sent to Crowdin when you save a draft or publish. Only fields that changed are uploaded again.
Translations in one click
Tick a checkbox to load translations as a draft or published version. Review changes first over REST, or queue them as Payload jobs. Missing required fields are not applied.