Introduction
Install PPROLint and activate it, then learn how its rules work and how to write your own.
PPROLint checks a Premiere Pro sequence against a set of rules and reports what it finds: an offline clip, a gap of black video, a clip scaled far beyond 100 %. Every rule, built-in or yours, is one small JSON file, a rule file. It names the items it looks at, the condition that makes an item a problem and the message to show.
{
"formatVersion": 1,
"id": "no-offline-media",
"name": "Offline media",
"description": "Reports clips whose source media is offline.",
"category": "static",
"scope": "clip",
"severity": "error",
"checks": [
{
"condition": { "field": "clip.source.offline", "operator": "equals", "value": true },
"message": "Clip \"{clip.name}\" on {clip.track} uses offline media \"{clip.source.name}\"."
}
]
}Read it as: for every clip, when its source media is offline, report an error on that clip with this message.
You don't need to write this JSON yourself: the rule editor, in the panel's settings, builds rules with menus and fields, and writes the file for you.
A rule file holds no code. PPROLint reads it with a fixed set of fields and operators, so a rule file you download from someone else can only inspect your timeline, never change it or reach anything else.
Where to start
Installing
Download PPROLint from your aescripts account, install it and open its panel.
Your license
Start the 7-day trial, activate your license, and where to turn for license questions.
Your first rule
Build a rule in the rule editor and see it report in Premiere, in ten minutes.
The rule editor
Every part of the editor: options, checks, conditions, messages, labels.
How rules work
Scopes, items, checks and unknown values: the model behind every rule.
Built-in rules
Every rule PPROLint ships with, with its complete rule file.
How these docs are organized
- Using PPROLint: installing, activating and managing your license and uninstalling. What changed in each version is in the changelog.
- Rule editor: Your first rule walks you through one rule in the editor, from an empty rule to a report in Premiere. The other pages cover each part of the editor, and Recipes gives complete rules to build.
- Rule files: the same rules written as JSON in a text editor, for sharing, version control or AI assistants. Your first rule file is the place to start.
- How rules work explains the model behind both.
- Reference lists everything a rule file can contain: properties, scopes, fields and operators.
- Built-in rules documents the rules PPROLint ships with. Their files are good starting points.
Using an AI assistant to write rules? See AI agents.
A question these pages do not answer? Write to support@pprolint.com.