Well… there was a solution 6 years ago!

https://multifarious.filkin.com/2016/07/28/handling-pdfs-is-there-a-best-way/

But I think the developers at transpdf found it quite tricky to work with the Studio API at the time (partially because the API was complex and partially because they were not really familiar with developing for this environment) and so didn’t maintain it. It is a shame, and in that 6 years things have moved on a lot.

Might be worth revisiting, although I’m not sure what the demand was like since it was a paid service and this is something I think is tricky to provide to the majority of translators unless they see a serious ROI.