irmion
ДовідкаLog in Знайдіть інструмент

PDF Документальний робочий банк

Inspect PDF/A declarations before validation.

Read the PDF/A identification fields declared in XMP metadata and collect basic document signals. Use the report before running a full archival conformance validator.

One unlocked PDF, up to 10 MB and 500 pages. Only upload a document you are authorised to process.10 MB Комбіновані межіA JSON report containing declared PDF/A identification fields, XMP parsing status, page count and pages with extractable text.
Зонка готується10 MB В поєднанні

Знайдіть один PDF І тут

Виберіть один розблокований PDFІ Джерело залишається незмінним, а результат завантажується окремо.

Selecting a PDF sends it to the API for inspection. Running the report sends it again for processing. These requests use memory and do not create a server-side file history.

Крок 2 / Конфігуруйте і виконайте

Configure PDF/A Compatibility Preflight

No PDF/A conversion is performed and no archival profile is selected. The operation inspects the supplied file.

Перевірка цього процесора.

Додаткових налаштувань не потрібноThis operation has no adjustable settings. Confirm the selected source and run it when processor status is available.
Запрошуємо до обробкиThe API holds selected files in request memory, returns Cache-Control: no-store, and does not create a server-side job history.

Продуктний контракт

розуміння PDF/A Compatibility Preflight до переробки

The processor reads the PDF/A identification namespace in XMP attributes or elements. A document title containing PDF/A is not treated as an identification marker.

01

Те, що ви надаєте

One unlocked PDF, up to 10 MB and 500 pages. Only upload a document you are authorised to process.

02

Що ви отримуєте

A JSON report containing declared PDF/A identification fields, XMP parsing status, page count and pages with extractable text.

03

Що потрібно переглянути

Metadata declarations can be incomplete or incorrect. The report does not validate embedded fonts, colour profiles, prohibited features or ISO conformance. Encrypted PDFs must be unlocked before processing.

Загальні використання

When PDF/A Compatibility Preflight is useful

Choose the report when you need to answer one of these questions before the next document step.

01

Inspect an archival export before formal validation.

02

Distinguish a PDF/A title claim from an XMP declaration.

03

Record missing or malformed XMP for a document-support request.

Практична допомога

Питання перед тим, як ви його запустили

Is a PDF/A marker enough for archival acceptance?

No. A marker is a claim inside the file. A dedicated validator must check the complete document against the required PDF/A profile, and your archive may impose additional requirements.

Will this convert an ordinary PDF to PDF/A?

No. It reads metadata and returns a report. Conversion is a separate operation and its output still requires validation before archival acceptance.

What does malformed or unsupported XMP mean?

The metadata could not be safely parsed or exceeded this check's supported limits. It is reported for review rather than treated as a valid declaration or proof that the entire PDF is unusable.

Документальний робочий потік

PDF/A Compatibility Preflight: a worked example

XMP declaring part 2 and conformance B is reported as a declaration. A PDF merely titled PDF/A has no marker unless matching identification metadata is present.

Keep the downloaded report beside the exact PDF you checked. If the document changes, run it again; the previous findings describe the earlier file, not the replacement.