How can we help?

Visit qurly.dev/register and create an account with email + password, or sign in with Google, Apple, GitHub, Phone, or any of the social providers we support. A personal workspace is created for you automatically; you can create or join additional business workspaces from Settings → Organization.

Click "Forgot password" on the sign-in page. We'll email a reset link valid for 15 minutes. If the email doesn't arrive, check your spam folder, then verify the email matches the address you signed up with.

Go to Settings → Account → Email. Enter the new address and click Update. We'll send a confirmation link to the new address; clicking it completes the change. The old address can no longer sign in once the new one is confirmed.

Go to /subscription in the app. Pick the plan you want and confirm. Upgrades take effect immediately and are prorated; downgrades take effect at the end of your current billing period. You'll keep access to your higher-tier features until the period ends.

We'll notify you when you reach 75% and again at 100%. After 100%, link/QR/landing-page creation pauses until the next billing cycle resets, OR until you upgrade. Existing links keep redirecting normally — only new creation is paused.

Major credit and debit cards via Stripe (Visa, Mastercard, American Express, Discover). Enterprise customers can pay by invoice; contact sales@qurly.dev.

Go to /subscription → Cancel plan. Cancellation takes effect at the end of the current billing period; we don't issue partial refunds. Your account stays active in read-only mode after cancellation so you can export your data.

Settings → Account → Delete account. Deletion is immediate and irreversible: short links stop redirecting, all data is purged within 7 days, and any teammates lose access to workspaces you owned. Transfer org ownership before deleting if you don't want this.

From the dashboard, click Create link. Paste the destination URL, optionally pick a custom slug (recommended for memorability), then Save. The link is live immediately.

Yes. Edit the link and change the destination URL — anyone clicking the existing short link is redirected to the new destination. This is the entire point of using a redirect layer; never paste a destination URL directly onto print or packaging.

Lowercase letters, numbers, and hyphens. 3-50 characters. Must be unique within your domain. Avoid words that look like spam (free-bitcoin-now), trademarks you don't own, and reserved words (api, login, admin, app).

Yes — Pro plans and above. Edit the link → Expiration → set a date. After expiry, clicks land on a fallback page or a destination of your choosing. Useful for time-bound campaigns.

Yes — Business plans and above. Edit the link → Password protection. Set a password; visitors are prompted before being redirected. Useful for partner-only links, customer-specific demos, and sensitive shares.

Same thing — "short code" is the technical term, "slug" is the marketing term. Both refer to the part after the domain (the "spring-sale" in acme.li/spring-sale).

Two ways. Via the in-app CSV importer (Settings → Import) — upload a CSV with destination, slug, and tags columns. Via the API — POST to /v1/links in batches of 100. Bulk creation requires Scale plan or above.

Open any link in your dashboard and click QR Code. Customise colour, shape, frame, and logo, then download as PNG or SVG. Every link can have an unlimited number of QR codes attached, in different styles.

Match size to the maximum scanning distance. Phone-in-hand (menu, business card): 1cm minimum. Arm's length (display, retail shelf): 2cm minimum. Wall-mounted poster: 5cm minimum. Out-of-home (billboard): 30cm minimum.

Most common causes, in order: (1) low contrast — black on white scans most reliably; (2) logo overlay too large — keep it under 25% of QR area; (3) printed too small for the scanning distance; (4) error correction set too low for the design (use level H if you have a logo overlay).

Yes — that's the whole reason you should put a Qurly short link behind every printed QR. Edit the underlying link's destination and every printed copy of the QR now redirects to the new destination, with no reprinting.

Yes. QR scans are tracked the same way as link clicks — total count, geo, device, time-of-day, referrer (when the scanner reports one). On Business plans and above, you also get city-level geo and device-type breakdowns.

Currently we focus on URL QR codes (which is most use cases). Wi-Fi and vCard QR types are on our roadmap. If you need them now, you can host a Qurly landing page that contains the Wi-Fi/vCard payload and put a regular URL QR on the marketing material.

From any link, toggle Landing page on, then build with the block editor. Drag blocks (heading, paragraph, button, image, vCard, embed) into place; click any block to edit it. Save when done — your short link now lands on the Qurly-hosted page instead of an external URL.

Heading, paragraph, button, divider, image, spacer, vCard, YouTube embed, X (Twitter) embed, and TikTok embed. We're continuously adding more — let us know what's missing.

The block editor renders a live preview as you edit. There's no separate "draft" state — the page is published the moment you toggle it on, but you can disable it temporarily by toggling the Landing page switch off.

Yes — Pro plans and above. Set up the custom domain in Settings → Domains, then any link/landing page on that domain renders at acme.li/your-slug. See our branded domain guide for the full setup.

A pre-built block layout for creators: heading + bio + 4-6 stacked buttons + vCard, ready to swap in your details. From the create-link screen, pick "Link in bio" instead of "Blank." Most creators ship a usable bio page in under a minute.

Yes — Business plans and above. In any image block, click "Generate with AI" and describe what you want. We use Gemini 2.5 Flash Image. Subject to per-org monthly quotas (Business 10/mo, Scale 100/mo, Enterprise unlimited).

Settings → Custom domains → Add domain. Enter the bare domain (no protocol, no path), grab the verification token, configure DNS at your registrar, then click Verify in Qurly. Full walkthrough in our branded domain guide.

Three: a TXT record at the apex containing the verification token, a CNAME at the apex pointing to proxy.qurly.dev, and an optional CNAME at www pointing to the same target. If your registrar doesn't support apex CNAMEs, use an A record instead — see the help center for the IP address.

DNS propagation is usually 5-15 minutes. Once propagated, verification is instant. SSL certificate issuance (via Let's Encrypt) takes another 1-3 minutes after verification. Total: typically 10-20 minutes from DNS save to live domain.

Yes, but you must turn off the Cloudflare proxy (the orange cloud) on the records pointing to Qurly. Qurly handles its own SSL termination; double-proxying breaks redirects. Set the records to "DNS only" (grey cloud).

Almost always either (1) DNS hasn't fully propagated yet (wait 10 more minutes), or (2) you have CAA records blocking Let's Encrypt. Check whether you have CAA records and either remove them or add `0 issue "letsencrypt.org"` to allow.

1 on Pro, 5 on Business, 20 on Scale, unlimited on Enterprise. Each domain is fully independent — you can have one for marketing campaigns, one for partner links, one for internal links, etc.

Timestamp, country and city (derived from a hashed IP), device type and OS, browser (where reported), referrer URL (where reported), and the link/QR's UTM parameters. We do NOT store raw IP addresses or any personally identifiable information.

Depends on plan: Free 7 days, Pro 30 days, Business 90 days, Scale 1 year, Enterprise 5 years. Older data isn't deleted catastrophically — it's archived and remains restorable on upgrade.

Yes — every plan can export click and scan analytics as CSV or JSON from Settings → Export. The Business plan and above also offer a streaming export to BigQuery / Snowflake / Databricks via our API.

Some scans don't lead to a page view — common on iOS, where the URL preview shows above the camera and users decide whether to tap. The gap is typically 10-25%. We track both numbers separately so you can see this delta.

Yes — on the Analytics page, switch the date selector to "Compare" mode and pick two periods (or two link folders). The dashboard shows side-by-side metrics with deltas.

Yes. UTM parameters on the destination URL are passed through unchanged. We also extract `utm_source`, `utm_medium`, `utm_campaign`, and `utm_content` into separate analytics dimensions so you can filter and group by them in our dashboard.

Settings → Organization → Members → Invite. Enter their email and pick a role (admin, editor, viewer). They get an invite email; clicking the link signs them in (or has them create an account) and adds them to the workspace.

Owner: full control, including delete the workspace and change billing. Admin: everything except delete and billing. Editor: create/edit links, QR, landing pages, but can't change settings or members. Viewer: read-only access to everything in the workspace.

Yes. Every account auto-gets one personal workspace. You can create or be invited to any number of business workspaces. The workspace switcher is in the top-left of the dashboard.

Yes — Enterprise plans. We use Supabase Auth's native SAML integration. Customer admins paste their IdP metadata URL (Okta, Microsoft Entra ID, Google Workspace, OneLogin, JumpCloud — any SAML 2.0 IdP works) and Qurly registers a per-domain SSO provider. Users with that email domain are then routed to the IdP at sign-in.

Not per individual link, but per folder — Business plans and above. Create a folder, set its visibility (Workspace / Admins-only), and any links in that folder inherit those permissions.

Yes. OpenAPI 3.1, accessible at api.qurly.dev with API-key authentication. Endpoints for links, QR codes, landing pages, analytics, organizations, and team management. API access requires Scale plan or above; free for Enterprise.

Settings → API → Create key. Pick the scopes (create_links, read_links, manage_qr, etc.) and an optional expiration date. Keys are shown once — copy and store somewhere secure.

Scale: 60 requests/min, 10,000/day. Enterprise: 600/min, 100,000/day, with bursts negotiable. Rate-limit headers (X-RateLimit-*) are returned on every response.

Yes — TypeScript and Python, both auto-generated from our OpenAPI spec. Install with `npm i @qurly/sdk` or `pip install qurly-sdk`. Source and docs at github.com/qurlydev.

Yes — Business plans and above. Configure webhook URLs in Settings → Webhooks for events like link.created, link.clicked (sampled), org.member_added. Payload is signed with HMAC-SHA256.

Native: Shopify (early access), Zapier, Make, Slack notifications. Coming: WooCommerce, HubSpot. The OpenAPI also makes it easy to roll your own integration.