Why we are building Prepta
Preflight software has been good for a long time. What it was never built for is the file the customer actually sends. A screenshot, a Canva export and a professionally prepared PDF all fail the same checks, and the operator is left doing the same diagnosis every day to work out which kind of failure this one is.
Prepta starts from that file rather than from an idealised one. It works out what arrived, checks it against the rules of the specific workflow it is going into, repairs what has exactly one correct answer, and stops where a decision is needed. The intention is not to be clever about artwork. It is to be predictable about it.
What we hold to
Say what it does, and what it does not
Every capability on this site is either available or marked as not available. Where Prepta cannot fix something, it says so instead of approximating.
The original is sacred
The customer file is preserved exactly as supplied. Repairs are new versions, always comparable against v1.
Automation is a permission, not a default
Nothing is transformed unless a production profile authorises it. Enabling automation is a per-rule decision made by you.
The operator stays responsible
Deciding whether a job is acceptable to print is a human judgement. Our job is to make that judgement fast and well informed.
Team, company registration, location and public social profiles (Organization sameAs) go here once confirmed. We would rather leave this empty than invent authority signals.
What you can verify today
The free PDF preflight, guides and comparisons are live — check a real file, read how we define bleed and PDF/X, and see how Prepta differs from Acrobat Preflight or PitStop. Named customer references will appear here only with permission.