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 결합된

1을 던져라 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.