HelloPDF - Generating a PDF from a URL has never been easier

@justinotherjohnson It could! It uses Chromium instances in the background to load everything. We wait until the page has fully loaded before rendering the PDF. Here's a PDF I just generated of my Twitter feed 😊. https://drive.google.com/file/d/...

@0x15f Very interesting. So if we know there are a finite (for example, 10) more items that can load on a page, you could walk it and make sure those items are on the PDF as well?

@justinotherjohnson While I'm not going to build something for a specific use case I am however working on a feature that allows you to run JS on the page before it's converted. You'll be able to create snippets on your dashboard and add "&snippet=mysnipid" to your url to run the code. That'll provide endless possibilities for all users who have to deal with lazy loading, hiding elements, walking the page, etc.

@0x15f Very cool. Thanks for the clarification.

@justinotherjohnson Added something that should fit your needs, you can execute JS on the page before its rendered as a pdf -> https://hellopdf.co/blog/post-bd....

@anderson760 As long as you have enough conversion seconds it should convert it just fine.

@anderson760 We convert PDF's using a Chromium instance, it won't render the PDF until all of the images have been loaded.

@0x15f Thanks, just tried it out. Any solutions for lazy loaded pages and images? Like the ability to scroll all the way then create the pdf?

@anderson760 I'll implement a query param that will do that 😄

@anderson760 Can you message me the website that's being converted so I can test it?

@unclejessy4real https://hellopdf.co/

@bpmarkowitz Sure. We handle conversions directly through an internal network of Chromium instances. No potentially sensitive information is stored, tracked, etc. We track API calls but do not track their origin or their target URL, we don't even store PDF's we stream them directly as they're requested. Any sensitive information on web pages is secure. We are PHI and HIPAA compliant.

@bpmarkowitz I'm using this with one of my clients in the medical industry as well so I understand the concern and need for compliance.

@jcalvarezjr Sure. We handle conversions directly through an internal network of Chromium instances. No potentially sensitive information is stored, tracked, etc. We track API calls but do not track their origin or their target URL, we don't even store PDF's we stream them directly as they're requested. Any sensitive information on web pages is secure.

@keirwilliams I'll add a demo page :)