I am experiencing an issue with the Document Translation API (api-version: 2025-12-01-preview) when translating PNG image files.

Question

API Endpoint:

POST /translator/document/batches

Issue Description:

PNG image translation fails consistently with the following error

{
    "id": "0ef5ccf0-2746-45e8-b712-24b165eeb675",
    "createdDateTimeUtc": "2026-03-10T10:20:56.3105795Z",
    "lastActionDateTimeUtc": "2026-03-10T10:21:07.7822589Z",
    "status": "Failed",
    "error": {
        "code": "InternalServerError",
        "message": "Document failed during parsing. If the error persists, report it with date/time of error, request identifier from response header X-RequestId, and client identifier from request header X-ClientTraceId.",
        "target": "Operation",
        "innerError": {
            "code": "InternalServerErrorDocumentParsing",
            "message": "Document failed during parsing. If the error persists, report it with date/time of error, request identifier from response header X-RequestId, and client identifier from request header X-ClientTraceId."
        }
    },
    "summary": {
        "total": 1,
        "failed": 1,
        "success": 0,
        "inProgress": 0,
        "notYetStarted": 0,
        "cancelled": 0,
        "totalCharacterCharged": 0,
        "totalImageCharged": 0
    }
}

Answer 1

This is how images are translated from Chinese to Korean.

Answer 2

PNG image translation with the Document Translation API using api-version=2025-12-01-preview is supported as part of the image translation preview feature.

The error payload shows:

• code: InternalServerError
• innerError.code: InternalServerErrorDocumentParsing
• message: "Document failed during parsing. If the error persists, report it with date/time of error, request identifier from response header X-RequestId, and client identifier from request header X-ClientTraceId."

This indicates a service-side parsing failure rather than a validation or configuration problem. For image translation with this preview API version, no additional configuration is required beyond submitting a supported image file type (such as .png) in a standard batch request.

Given that:

• .png is explicitly listed as a supported image format for this preview.
• The error is an internal parsing error with zero characters/images charged.

The next step is to follow the guidance in the error message and report the issue to Microsoft with:

1. Date and time of the failure.
2. The X-RequestId value from the HTTP response headers.
3. The X-ClientTraceId value from the request headers (if set).
4. The failing PNG sample (or a minimal repro file) and the exact api-version and endpoint used.

This will allow the product team to investigate the parsing failure in the preview image translation pipeline.

---

References:

• Start batch translation
• Get status for a specific translation job
• Get status for all translation jobs
• Get status for a specific document
• Cancel translation
• DocumentTranslationGetDocumentsStatus400Response interface
• DocumentTranslationGetDocumentsStatus404Response interface
• DocumentTranslationGetTranslationsStatus500Response interface
• Microsoft Foundry publish to Teams Bot service error - Microsoft Q&A
• Missing api-ms-win-core-winrt-l1-1-0.dll - Microsoft Q&A
• Azure Deployment Takes 70 Minutes to Fail with Obscure Error - Microsoft Q&A
• Can someone please explain why Microsoft Foundry agents cannot take in pdfs and jsons as inputs when it says its allowed - Microsoft Q&A
• pdf error from word - Microsoft Q&A