The right plan for
every workflow

Credits are the unit of work in Utified. Different tasks cost different amounts based on complexity. Your plan refill is automatic every month on your billing date.

Absolutely. You can upgrade or downgrade at any time. Changes are reflected immediately, and we prorate any existing payments.

We offer prorated refunds for both monthly and annual plans, calculated per-day from the cancellation date through the end of the current billing period. Cancel anytime from Account → Billing. See the full Refund & Cancellation Policy at /refunds.

Your subscription enters a 7-day grace period during which your plan stays fully active and Stripe automatically retries the charge. If payment is still not collected after 7 days, your account downgrades to Free.

All paid plans (Starter, Pro, Max) include email support with a 24-hour response time on business days. Free accounts get access to docs, FAQ, and best-effort community support. Send a support request anytime at /support.

Credits reset each month to ensure everyone has a fresh quota for their projects. Pro and Max plans offer high enough limits that you rarely need to worry.

We use Stripe and PayPal to process payments securely. We never store your card information on our servers.

Drops are public file reception links you create and share with anyone - no account needed to send files. Files arrive auto-converted to whatever format you configured. Drops are available on all paid plans (Starter, Pro, Max).

Receiving files through a Drop consumes a small amount of credits for processing and storage. Upload cost is ~0.01 credits/MB and storage is billed at 1.5 credits/GB/month with 1 GB free for paid plans.

All paid plans - Starter, Pro, and Max - include API access. Free accounts cannot use the API. Each plan has different rate limits: Starter gets 2 req/s, Pro gets 5 req/s, and Max gets 25 req/s with 25 concurrent jobs.

At /docs/api/tools you'll find a card for every server-processed tool (image, audio, video) with the exact endpoint, required scope, request body fields, expected response, and copy-paste cURL / Node.js / Python samples. The full API surface (auth, rate limits, webhooks, errors, drops) lives under /docs/api.

Yes. Tool pages open with an AI-citation-friendly Answer Capsule: a structured "What it is / When to use it / How to use it" block paired with HowTo, FAQPage, and SoftwareApplication schema.org JSON-LD. This makes Utified content easy for ChatGPT, Perplexity, Google AI Overviews, and traditional rich-result crawlers to quote and link back to.

Yes. Every completed or failed tool job can produce an HMAC-SHA256-signed JSON receipt containing the tool, input URL, options, output URL, credit cost, and timestamps. Download it from your Account → Activity Feed (Receipt button next to recent jobs) or via GET /api/v1/jobs/<id>/receipt on the API. Receipts are available while the job is still in queue - typically 24h after completion. Useful for compliance, audits, and tamper-evident downstream automation.

Open /reverse, paste the receipt JSON, and click Verify. The HMAC signature is checked server-side (the secret never leaves our servers) and you get a clear valid / invalid result plus a breakdown of which tool, options, input, output, and timing the receipt covers. Works for both per-tool job receipts and chain run receipts. No account required.

Yes. Every API job uses the same credit pool as the web app. You can set per-key daily and monthly spend caps from your account to prevent unexpected usage.

Yes. You can create up to 10 live keys and 1 test key per account. Each key can have its own scopes, spend caps, and IP allowlist - ideal for separating environments or clients.

Yes. All paid plans include Drops API access. You can create and configure drops, list submissions, download received files, and mark items read or starred - all via Bearer token. Use the drops:read and drops:write scopes to restrict key permissions.

Drops are the inbox - senders push files in to you. Living Files are the same files, but exposed at a permanent /f/<token> URL where anyone with the link can re-run tools (compress, convert, resize, etc.) on demand without re-uploading. Drops = file intake; Living Files = file output that stays useful long after the upload.

Living Files are included free with any paid plan that has Drops (Starter, Pro, Max). The toggle "Allow public transforms" is in every drop's processing settings. Free plan does not include Drops and therefore cannot use Living Files.

You, the file owner, pay. Visitors never pay and never need an account. Each transform deducts credits at the same rate as running that tool yourself - the same credit cost as a normal job.

Open the submission in your drop inbox, click "Generate share link" in the Living File panel. You get a /f/<token> URL to share. You can also force-enable or force-disable transforms per submission, override the drop default, or revoke the link at any time.

Yes. Only one transform can run at a time per shared file - subsequent requests return 409 until the in-flight one finishes. You can also revoke the share link instantly, which stops the URL from working immediately. The downloaded transform output is unaffected.

The API returns a 429 status with a Retry-After header. Your job is not dropped - simply retry after the indicated seconds. Concurrent job limits work the same way.

A Chain is a saved pipeline that runs several tools in sequence on a single input. For example: resize image → convert to WebP → compress. Chains run in the cloud, can be triggered from the web, the API, a schedule, an inbound webhook, or a Drop submission - and produce one signed receipt at the end.

Pro and Max. Free and Starter accounts can still run public Chains shared with them via a /c/<slug> link, but only Pro and Max can save, schedule, embed, fork, or trigger Chains they own.

Each step costs the same credits as running the equivalent tool individually. Pro accounts get a 10% discount on the total step cost, applied as a refund at the end of every successful run. Max accounts pay 50% of the total step cost - the lowest rate available. Chain billing happens whether the run succeeds or fails partially; only completed steps are charged.

Yes. Set a Chain's visibility to "unlisted" or "public" and share the /c/<slug> link - anyone with the URL can run it without an account. Visitors do not pay; you, the chain owner, are billed for each run. You can also embed it on any third-party site with <iframe src=".../c/<slug>/embed">.

Yes, on Pro and Max. Each Chain can have one or more schedules: every N minutes (minimum 5), daily at a fixed time, or weekly on a specific day. The schedule fires the chain against a fixed input URL each time. Schedules auto-disable after 5 consecutive failures to prevent retry storms.

Yes, on Pro and Max. In a drop's settings, pick any of your saved Chains under "Run a Chain on every submission". Each uploaded file will be piped through that Chain automatically; the processed result appears in the drop submission as usual.

Each Chain can issue a unique webhook URL. POST to it with { "input": { "file": "<url>" } } and it fires a run as you. Useful for Zapier, Make, IFTTT, GitHub Actions, or any service that sends webhooks. Rotate or revoke the token at any time from the Chain detail page.

Every completed Chain run can produce a downloadable JSON document with the chain version, step outputs, timing, credit cost, and an HMAC-SHA256 signature. The receipt is tamper-evident and can be verified by anyone who has Utified's public verification key - useful for compliance, audits, or downstream automation that needs cryptographic proof a chain ran with specific settings.

Yes. Click Cancel on any run that is queued or in progress. The in-flight step finishes (BullMQ jobs cannot be aborted mid-execution safely), then the chain stops cleanly without starting any subsequent step. Already-completed steps are not refunded.

Yes. Pro and Max accounts can manage and run Chains via Bearer-token API at /api/v1/chains. Use the chains:read, chains:write, and chains:run scopes to restrict key permissions. Schedules and inbound webhook URLs are also visible per-chain.

Paste a list of file URLs (one per line), pick any server-processed tool (image-convert, audio-trim, video-compress, etc.), and Utified runs all of them in parallel. You get a live status table with per-row download links — no need to upload each file individually.

All paid plans. Starter: up to 10 URLs per batch · Pro: 50 · Max: 200. The Free plan does not include batch processing.

Each URL costs exactly the same credits as running the equivalent tool individually — no markup, no batch fee. Max users pay 0 (their existing unlimited credit applies). Only successfully processed URLs are billed; failed items refund as they would for a single job.

Yes. Cancelling marks queued items as skipped (never enqueued, never billed). Items that were already running let their job finish — they reconcile to succeeded/failed on the next status poll and bill normally on success.

Yes. A growing set of client-side utility tools (JSON formatter, Base64, JWT decoder, regex tester, hash generator, color converter, URL encoder, UUID generator, markdown to HTML, lorem ipsum, case converter, text counter) can be embedded into any website via a one-line <iframe>. No account, no API key, no credits. Visit any supported tool page and click "Get embed code" to copy the snippet.

No. Embed widgets are 100% free on every plan, including the Free plan. They run entirely in the visitor's browser - no server processing, no credit deduction. There is no API key required.

Yes. The "Get embed code" panel lets you toggle the "About this tool" content block and the "Related tools" section before copying. The Utified backlink in the footer stays so you (and we) get the SEO benefit of the embed.

Currently 12 tools: JSON formatter, Base64, JWT decoder, regex tester, hash generator, color converter, URL encoder, UUID generator, markdown-to-HTML, lorem ipsum generator, case converter, and text counter. Server-processed tools (image compress, PDF tools, etc.) are planned for a future phase since they need API key billing.