Thanks for pointing this out. You’re right - some assets are currently loaded at runtime, which can cause actions to hang if the internet is cut mid-session. All PDF processing itself happens locally in the browser, and as you noticed, serving the page locally works fully offline. Improving offline behavior and making this easier to verify is on the roadmap