What JSON Lines is
JSON Lines is one complete JSON object per line, with no enclosing array and no commas between records. The file is not valid JSON as a whole, and that is the point.
Log pipelines, machine learning datasets and anything that appends records or reads them in a stream.
What PDF is
PDF describes a page: glyphs at coordinates, not rows and columns. A table in a PDF is a visual arrangement, not a data structure.
Reports, invoices, statements and anything sent to be read rather than processed.
What changes when you convert JSON Lines to PDF
Each line is parsed on its own, so a corrupt record does not take the file with it. Keys are unioned across lines in first-seen order, so a record missing a field leaves that cell empty rather than shifting the columns.
The table is drawn into a paginated document with the header repeated on every page, so a long table stays readable past page one. Page size, orientation and font size are all adjustable.
What carries over from JSON Lines to PDF
JSON Lines records 5 things about a table that PDF has no way to hold.
JSON Lines knows which of its values are numbers. PDF keeps only their appearance, so nothing downstream can sort or sum them without someone reading them back off the page first.
An empty cell and a missing one are the same thing in PDF, so a null and an empty string in the JSON Lines both come out blank and can no longer be told apart.
JSON Lines can hold a value that is itself a list or an object. PDF has only flat cells, so nested values are flattened into one cell rather than being spread across columns.
JSON Lines can be read one record at a time. PDF has to be complete before it means anything, so the whole table is held in memory while it is written and a file that gets cut off part way through is not partly usable - it is unusable.
PDF is the end of the line for this data. Reading the table back out of it is a separate and much harder problem than writing it, so keep the JSON Lines if you will need the values again.