Inspect PDF

The pages and their sizes, the PDF version, whether the file is encrypted, linearized, tagged, PDF/A or a form; its properties (title, author, application, dates); where the bytes go - images, fonts, page content, attachments, metadata, structure; the images with the resolution they are drawn at and how many exceed 300 dpi; the fonts, which are embedded and which a reader must substitute; the text layer page by page; the annotations; the hidden data; and whether the structure is sound. Then the tools the findings point at.

The right column says: images drawn at more than 300 dpi or making up most of the file point at Compress, hidden metadata or attachments at Sanitize, pages without text at OCR, a filled form at Flatten, a damaged structure at Repair. Each is a link.

No. Nothing is written, so there is no output and it does not count against the daily limit.

No. The file is read in your browser, on your device; nothing leaves it.

The report answers that directly: the bytes are split by what they are - images, font programs, page content, attachments, metadata, structure - so you see at a glance whether it is twenty photographs or thirty font subsets. Each finding links to the tool that deals with it.

It reports what the file claims - the PDF/A part and conformance it declares, and whether it is tagged - but it does not check those claims against the standard. A formal verdict needs a validator such as veraPDF; this is a look at what is in the file.