Skip to main content
Filecheck ships six official libraries. The browser packages are thin, typed wrappers around the Element — the Element itself always loads from the Filecheck CDN, so UI updates reach you without a package upgrade. The server packages wrap the REST API with typed clients, retries, and a one-call job verification helper.

Install

Which do I need?

A complete integration has two halves, and you typically pick one package from each:
  1. Client — embed the Element so customers upload, see findings, and get auto-fixes. Use filecheck-js on vanilla stacks, or filecheck-react / filecheck-vue inside those frameworks. Gate your submit button on canProceed and carry the jobId to your server.
  2. Server — before fulfilling, verify the submitted jobId with your secret key. Use filecheck-node or filecheck/filecheck-php; both encode the verification checklist in a single verify() call.
Working from an AI agent instead of a storefront? filecheck-mcp gives ChatGPT, Claude, Cursor, and other MCP clients tools to check and fix files and to set up workflows, rules, profiles, products and delivery. See the AI agents section.
Not on npm or Composer? The plain <script> embed works everywhere — see Element on a custom stack. No browser in the flow at all? Use the headless API integration.
All packages are MIT licensed and developed in the open at github.com/PrintApp/filecheck-integrations (PHP: github.com/PrintApp/filecheck-php).