Nirmion
Help Find a tool

PDF and document workbench

Read observable PDF encryption and permission flags.

The processor reads the permission mask exposed by the opened PDF and decodes standard flag bits.

One readable PDF; files requiring a password must be unlocked before processing.10 MB combined limitOne JSON report with encryption state, numeric permission mask, and eight named permission signals.
Drop zone ready10 MB combined

Drop one PDF here

Choose one unlocked PDF. The source remains unchanged and the result downloads separately.

Files are sent only when you run the tool; no server-side job history is created.

Step 2 / configure and run

Prepare PDF Permissions Report

Select one source and confirm the processor is available before running this bounded operation.

Checking this processor...

No extra settings requiredNo settings are required. The operation examines the complete bounded document using one fixed rule.
Request handlingThe API processes the selected file in request memory, returns Cache-Control: no-store, and creates no server-side job history.

Product contract

Understand PDF Permissions Report before processing

The processor reads the permission mask exposed by the opened PDF and decodes standard flag bits.

01

What you provide

One readable PDF; files requiring a password must be unlocked before processing.

02

What you receive

One JSON report with encryption state, numeric permission mask, and eight named permission signals.

03

What to review

Flags do not establish ownership, authorization, enforceability, or legal permission to use content.

Workflow

From source to checked download

Use PDF Permissions Report on a working copy and review the separate result.

1. Select

One readable PDF; files requiring a password must be unlocked before processing.

2. Configure

No hidden presets or inferred selections are applied; the complete supported structure is processed.

3. Verify

Open the download and verify its schema or document behavior. Flags do not establish ownership, authorization, enforceability, or legal permission to use content.

Worked review example

How to interpret PDF Permissions Report

The report can distinguish copy, annotate, assemble, form, and high-quality print flags.

01

Observed input

One readable PDF; files requiring a password must be unlocked before processing.

02

Expected artifact

One JSON report with encryption state, numeric permission mask, and eight named permission signals.

03

Interpretation boundary

Flags do not establish ownership, authorization, enforceability, or legal permission to use content.

Example output

A concrete verification target

The report can distinguish copy, annotate, assemble, form, and high-quality print flags.

encrypted: false
copy: true
modify: true
print_high_quality: true

Implementation reference:PyMuPDF PDF API documentation

Common uses

When PDF Permissions Report is useful

Read observable PDF encryption and permission flags.

01

Record permission settings during intake.

02

Compare protected and distribution copies.

03

Diagnose why a compliant viewer disables an action.

Important boundary

Keep the source until review is complete.

Flags do not establish ownership, authorization, enforceability, or legal permission to use content.

Practical help

Questions before you run it

What does PDF Permissions Report actually inspect or change?

The processor reads the permission mask exposed by the opened PDF and decodes standard flag bits. It processes only the supported structures found in the selected PDF and returns a separate download. It does not overwrite the source, infer missing document intent, or certify legal, archival, accessibility, privacy, or security status. Review the artifact against the original before using it in another workflow.

What limits apply to PDF Permissions Report?

One readable PDF; files requiring a password must be unlocked before processing. The request is limited to 10 MB, the document to 500 pages, discovered structures to 10,000 items, and generated output to 50 MB. Password-protected files must be unlocked first. Malformed, application-specific, or unsupported PDF objects may require a specialist desktop application and manual inspection.

What should I verify after PDF Permissions Report finishes?

Confirm the download opens and matches the stated output, then compare page count, visible content, navigation, form behavior, and any task-specific structure with the source. Flags do not establish ownership, authorization, enforceability, or legal permission to use content. Keep the original until the result has been tested in the viewer, print process, records system, or downstream application where it will be used.

Document workflow

PDF Permissions Report with inspectable boundaries

Read observable PDF encryption and permission flags. The processor reads the permission mask exposed by the opened PDF and decodes standard flag bits. One readable PDF; files requiring a password must be unlocked before processing.

One JSON report with encryption state, numeric permission mask, and eight named permission signals. Flags do not establish ownership, authorization, enforceability, or legal permission to use content. Completed downloads remain only in this browser tab for limited re-download.