Connectors

Direct upload

Optimize files without connecting a platform.

You don't need a connector to use Inverity. Upload files directly to the dashboard, and download the optimized results.

When direct upload is the right tool

  • Evaluating Inverity before you're ready to give it access to a production library.
  • Your platform isn't supported yet. See CMS connectors and DAM connectors for the current list, and tell us what you use.
  • One-off work — a launch batch, a set of hero images, a video for a campaign — that doesn't live in a connected system.
  • Assets from a system you deliberately don't want connected, for policy or approval reasons.

How it works

Upload your files in the dashboard. They're processed with the same pipeline as connected sources: content detection, engine routing, quality check. Results appear with the same original size, optimized size, and savings figures. See How optimization works.

If an asset can't be improved at equivalent quality, it's skipped and your original comes back unchanged.

Volume works the same way

Uploads and connected-source optimization draw from the same monthly volume budget, metered by source file size. There's no separate allowance for uploads and no discount for them. See Volume and usage.

The trade-off

Direct upload is manual by definition. You upload, you download, you put the files back wherever they came from — and you do that again next time.

A connector does all of that automatically and continuously: new media in a watched location is optimized without anyone remembering to do it. If you find yourself uploading the same kind of asset repeatedly, that's the signal to connect the source instead.

Uploads are a good way to test a profile

Before changing the quality profile on a connected production library, upload a handful of representative assets and compare the output. Nothing is written back to your platform, so there's nothing to undo if you don't like the result.

Previous
Tokens and permissions