Poor performance on scanned PDFs with improperly rotated content #217

Open
opened 2026-02-16 00:17:10 -05:00 by yindo · 1 comment
Owner

Originally created by @invakid404 on GitHub (Jul 30, 2024).

Describe the bug
I noticed that when dealing with a scanned PDF with improperly rotated content, LlamaParse consistently gets certain details like numbers wrong, sometimes swapping out certain digits for others, repeating digits, etc.

It is consistently reproducible with caching disabled and rotating the PDF has a noticeable performance improvement.

I managed to make a reproduction by generating 50 random numbers, putting them in a PDF, converting them to an image, and then comparing the output when the PDF is correctly oriented and when it is not. In the first scenario, all numbers in the output are correct. In the second scenario, it outputs the correct amount of numbers, and some of them are incorrect.

Files
numbers_normal.pdf
numbers_rotated.pdf
The original numbers

Job ID
If you have it, please provide the ID of the job you ran.
You can find it here: https://cloud.llamaindex.ai/parse in the "History" tab.

Screenshots
Feel free to also provide screenshots if relevant.

Client:
Please remove untested options:

  • Frontend (cloud.llamaindex.ai)
  • Typescript Library

Options
Multimodal with Claude 3.5 Sonnet

Additional context
I did see #32 before opening this issue, but I thought that my case was different enough for this issue to not be considered a duplicate. I also have specific reproduction steps which I thought are worth sharing.

Originally created by @invakid404 on GitHub (Jul 30, 2024). **Describe the bug** I noticed that when dealing with a scanned PDF with improperly rotated content, LlamaParse consistently gets certain details like numbers wrong, sometimes swapping out certain digits for others, repeating digits, etc. It is consistently reproducible with caching disabled and rotating the PDF has a noticeable performance improvement. I managed to make a reproduction by generating 50 random numbers, putting them in a PDF, converting them to an image, and then comparing the output when the PDF is correctly oriented and when it is not. In the first scenario, all numbers in the output are correct. In the second scenario, it outputs the correct amount of numbers, and some of them are incorrect. **Files** [numbers_normal.pdf](https://github.com/user-attachments/files/16430237/numbers_normal.pdf) [numbers_rotated.pdf](https://github.com/user-attachments/files/16430238/numbers_rotated.pdf) [The original numbers](https://gist.github.com/invakid404/7a7d2f8ad70b20a428dd2ff116db9b59) **Job ID** If you have it, please provide the ID of the job you ran. You can find it here: https://cloud.llamaindex.ai/parse in the "History" tab. **Screenshots** Feel free to also provide screenshots if relevant. **Client:** Please remove untested options: - Frontend (cloud.llamaindex.ai) - Typescript Library **Options** Multimodal with Claude 3.5 Sonnet **Additional context** I did see #32 before opening this issue, but I thought that my case was different enough for this issue to not be considered a duplicate. I also have specific reproduction steps which I thought are worth sharing.
yindo added the bug label 2026-02-16 00:17:10 -05:00
Author
Owner

@hexapode commented on GitHub (Jul 30, 2024):

thanks for repporting, we need to improve on rotated content.

@hexapode commented on GitHub (Jul 30, 2024): thanks for repporting, we need to improve on rotated content.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_cloud_services#217