Find quick answers about Pixy, from getting started and editing your website to collaboration, integrations, and everything in between.
A visual editor that runs on your own website. You open design mode on the real page, change what you see, and your coding agent turns those changes into code. Your repository stays the source of truth.
A design tool draws a picture of your product and hands you an export to reproduce. In Pixy the running page is the workspace, so you work with your real content, your real logged-in states and your own CSS. Nothing is redrawn.
No. An edit becomes a draft record addressed to a place in your code. The site changes when your agent or your developer builds that record and you ship it.
No. A person can read the edits and build them by hand. An agent is simply faster, and any tool that can send an HTTP request can pull the work.
This site runs Pixy. Press ⌘⇧E on the home page and edit it. What you do stays in your browser and disappears when you reload.
One script tag in the <head> of your site. No build step, no package, nothing to run. The snippet on your project card already carries your project key. See Install.
All of them. Pixy attaches to the page after your framework has rendered it, so React, Next, Svelte, Astro, Django and Shopify are the same job, and so is anything else that ends up as a page. See Compatibility.
Yes. The Chrome extension works with no tag on the page.
Yes, and on staging and production too. Pixy has no idea what an environment is. An edit is scoped by the browser you approved and the URL you are on, so the same tag goes everywhere you design.
Yes. The key in the tag names the project and grants nothing. For a visitor who has not approved that browser, which is everyone, the loader reads one value out of local storage and stops. What it costs them is a small cached file.
No. The button only shows when the address carries ?pixy-connect, which you add yourself to connect your browser. See Authorize.
⌘⇧E on any page of a site you have approved. Esc closes it.
Position, size, rotation, order, color, type, spacing, text and images, and you can draw new elements straight onto the page. When you want the rule underneath, the CSS and HTML panels are right there.
All of them, when that is where the color lives. Every edit records what it is aimed at: a CSS rule, a color in the design system, one element on one page, or the page itself. Your agent reads that target instead of guessing, so a classed button is changed once, at the component.
You resize the artboard and your own media queries answer. Nothing is simulated, and every change remembers the width you made it at, so a base style is never mistaken for a breakpoint.
Yes, and undo walks your own steps. It stops where a teammate's step begins rather than skipping over it, so you cannot take back somebody else's work. The owner can walk anyone's.
Parallel lines of edits on one project, each with its own undo history. Try three headers as three versions, then share one, some or all of them on a link.
Press C and write on whatever is selected, or on the page when nothing is. The note travels with the visual edits and stays on the page as a pin. "Make this the primary button" is easier said than dragged.
Screenshots at any size, including the full page, and video recording with an optional face bubble. Neither is limited on any plan.
Any of them. Claude Code, Cursor, or anything that can make an HTTP request. There is nothing to install on the agent's side.
Press Connect coding agent in the Pixy menu, copy the instructions and paste them into your agent. The invitation inside works once and expires in ten minutes, so no lasting secret goes through a chat window. The card says connected as soon as the agent signs up. See Agents.
You design, then you tell your agent to check Pixy. It pulls with its own key, builds what it finds, answers in the thread and acks each record when it is done. Nothing is copied by hand.
Nothing is lost. A pull does not close a record, only an ack does, so an unfinished batch comes back on the next pull. The lock it was holding can be released from the panel.
Only when you want a titled batch with a conversation on it. Otherwise just edit. The agent names a task itself when it acks, and files the finished work into it.
Yes, one per person if you like. The panel lists each agent, what it is building and when it last pulled. Removing one refuses its next call, and everything it already built stays.
One, at api.pixydesignapp.com. Every call is a POST with JSON and the key in an X-Pixy-Key header, and every documentation page is served as plain .txt so an agent can read the API itself. Calls are unlimited on every plan. See API.
One project's edits, conversation and images. Not your account, not your other projects, not your billing, and never your site directly.
Send a shared link. Your site opens with your edits on it and they can walk around as though the design were live. No account, no extension, nothing to install.
From half an hour to a day at one press, or a span you set yourself. Two hours by default. You can keep it to named email addresses instead of anyone holding the URL, and delete it whenever you want.
A shared link with Live turned on. Whoever opens it watches you work on the real site: your cursor, your clicks, your edits as they commit, the pages you open. Chat, microphone and camera are in the bar. Nothing is recorded. See Live.
Yes. A viewer follows your viewport by default and can stop following at any point, keeping their own scroll and their own page while still seeing your cursor and your edits.
A project has an owner and any number of members, invited by email address. Nobody accepts anything, the project is simply there next time they sign in. Roles run from viewer to editor, and a manager runs the work and the agent keys without ever touching the page. See Teams.
No. Teams cost nothing to form, and everyone joins with the permissions of their own plan. A role you grant is capped by that person's plan, so a Free account invited as an editor works as a viewer until it upgrades. On the project you own you always have everything.
The project key px_ is public and only names the project. The browser approval pxt_ is the one that grants editing, and it exists in that browser, for that site, alone. The agent key px_sk_ is your agent's private credential. Reading your HTML gets a stranger the project's name and nothing more.
Very. Approving https://acme.com does not approve staging.acme.com or localhost:3000, and your laptop and your phone are two approvals. Each lasts 180 days from its last use, so a browser you stop designing on lapses by itself.
Regenerate key on the project card. It mints a new project key and drops every agent key, every browser approval and any connected page. Your pages, edits and tasks survive, but every deployed tag needs replacing.
No. We never capture, copy or store them. The editor runs in your browser on your site, and only the record of what changed leaves it. Nothing on our side fetches a page, which is why localhost and sites behind a login work at all.
No. Your agent runs on your own machine under your own provider account, and Pixy is the relay between the two. We send your work to no model and run none of our own.
None, and no third-party analytics or trackers. Even the fonts are served from our own server. See the Privacy Policy.
There is not. You type your email, we send a six-digit code that is good for ten minutes, and the code signs you in. A new address becomes an account on the same screen.
The whole editor on your live site, unlimited edits, unlimited API and MCP calls, screenshots, recording and versions. One project, a design system read from 5 pages, and 3 months of history after a pull. No card.
$29 a month for unlimited projects, a design system read from 20 pages, and 6 months of history. See Pricing.
Accounts for people who work on the site without designing it. Manager, $10 a month, runs the work: comments, tasks, members, links, Live and agent keys. Writer, $19 a month, adds the page's words and images, never the layout. Both hold unlimited projects.
The plan above Pro, not on sale yet. Animation on the live page, components and shared assets, a design system read from every page, shipped as real CSS. Leave your email on the card and we will tell you when it opens.
Not while you stay subscribed. Launch prices rise as Pixy grows and yours stays where it started. Tax is included.
Any time, from your billing page. Cancel and the plan runs out the period you already paid for. End now stops access today and refunds the unused part to the card that paid. Plan switches are prorated both ways, so you never pay for the same days twice. See Refunds.