Bug Report: JavaScript Error on Bulk Upload of Non-Image Files in Media

[roi-polisave]

Describe the Bug

When attempting to bulk upload non-image files (such as .csv, .pdf, or .xlsx) to the Media collection in the PayloadCMS Backoffice, a JavaScript error occurs. The issue does not occur when uploading image files (e.g., .jpg, .png).

This happens on a clean version of a system, without any code changes.

ERROR: Unexpected end of JSON input
    err: {
      "type": "SyntaxError",
      "message": "Unexpected end of JSON input",
      "stack":
          SyntaxError: Unexpected end of JSON input
              at JSON.parse (<anonymous>)
              at parseJSONFromBytes (node:internal/deps/undici/undici:6571:19)
              at successSteps (node:internal/deps/undici/undici:6545:27)
              at node:internal/deps/undici/undici:1211:60
              at node:internal/process/task_queues:140:7
              at AsyncResource.runInAsyncScope (node:async_hooks:206:9)
              at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)
              at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    }

Link to the code that reproduces this issue

https://github.com/roi-polisave/payloadcms-test/tree/main

This happens on a clean version of a system, without any code changes.

Reproduction Steps

1. Go to the Media collection in the Backoffice.
2. Drag and drop a non-image file (e.g., .csv, .pdf, or .xlsx) into the bulk upload area.
3. Observe the JavaScript error in the console.

Which area(s) are affected? (Select all that apply)

Not sure

Environment Info

React: 19
Payload: 3.15.0 - but also lower versions
Next.js: 15.1.0 - 15.1.3
Node.js: 22.12.0 and 20.17.0

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@beta -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload