Build, test and export your PAC file
Import an existing PAC file or click together rules from simple building blocks. Test right in the tool which URLs route where, then export the finished file - for Zscaler hosting or self-hosting.
Your PAC file never leaves your machine: everything runs in the browser, no data transfer.Import an existing PAC
Paste the text or choose a file. Standard rules (private networks, domains, glob patterns, weekday bypass) are recognized automatically.
Rules
Active rules in fixed rank order (private networks/realm first, default forward structurally last). Disable instead of delete.
Generated PAC source
Check against test URLs
Uses the same evaluation engine as the PAC Tester.
Choose export variant
For Zscaler hosting (recommended)
The ${GATEWAY} variables stay in place and are automatically substituted by Zscaler with the nearest access point (geo-routing, subcloud pinning and failover are preserved). Upload under Administration → Hosted PAC Files.
For self-hosting
The gateway variables are replaced with fixed values.
Build and test it here.
CentaurNexus supports controlled individual changes in approved Zscaler workflows – with tenant policy, audit and read-back.
View product demoFrequently asked questions
It lets you click together a PAC file from simple rules or import an existing PAC file, check the rules right in the tool against test URLs, and export the finished file - either for Zscaler hosting (gateway variables stay in place) or self-hosting (gateway values are substituted with fixed ones).
They aren't lost. Anything the import can't translate into a rule stays as an unchanged text block at its original position and is put back unchanged on export. The tool visibly reports how many lines this affects.
Through an automated round-trip test: the imported and the newly exported version are both actually executed against the same list of test URLs. If all results match, the round trip is lossless. The tool shows the result right after import.
Zscaler hosting leaves the ${GATEWAY} variables in place - Zscaler automatically substitutes them with the nearest access point when serving the file (geo-routing). Self-hosting replaces these variables with fixed values you supply - this loses geo-routing, subcloud pinning and automatic failover, which the tool clearly flags.