1. Open My Projects and select the project.
2. Read the error message and use Retry if it is available.
3. If your request is very broad, revise it around one clear goal and the features needed to accomplish it.
4. If the same error happens again, contact support with the project ID and the exact error shown.

You may leave the page while a build is processing. Check My Projects for its current status. Do not start several copies of the same project. If the status does not change after a reasonable wait, send us the project ID.

Do not keep spending time repeating the same step. Try one retry, then check whether your instructions contain conflicting features or missing details. If it fails again, use the support link below and include your project ID. This lets us inspect the correct build instead of guessing.

Use a revision and describe the difference between the current behavior and the behavior you expected. Focus on the goal, where it should work, what should trigger it, and what the result should be. Test each revision before requesting another change.

Sign in and open My Downloads. If the build just finished, refresh the page once. Make sure you are signed into the same account used to create the project.

Return to My Downloads and use the current download button instead of an older browser tab or saved temporary link. If the new button also fails, contact support with the project ID.

Chrome’s Load Unpacked feature needs a normal folder containing manifest.json and the extension files. Download the ZIP, choose Extract or Unzip, then select the extracted extension folder in Chrome—not the ZIP file itself.

Select the folder that directly contains manifest.json. If you open the folder and only see another folder, go one level deeper. Do not select your entire Downloads folder.

1. Download and extract the ZIP.
2. Open chrome://extensions.
3. Turn on Developer mode.
4. Select Load unpacked.
5. Choose the extracted folder containing manifest.json.

See the complete Load Unpacked guide.

The wrong folder was selected, the ZIP was not extracted, or the manifest is missing. Open the extracted files and locate manifest.json, then select the folder containing it. If no manifest exists, contact support with the project ID.

Remove the extension from chrome://extensions, download a fresh copy, extract it again, and retry. If Chrome still shows the error, copy the complete red error message and send it with your project ID.

Open chrome://extensions and click the reload icon on the extension card. Then refresh the webpage where you are testing. Some background or permission changes may require removing and loading the extension again.

Confirm you are testing on a page the extension is allowed to access. Reload the extension and then reload the test webpage. If the extension has a toolbar button, pin it and open it. Note the exact page and action that failed before requesting a revision.

The website may not be included in the extension’s allowed site matches, or Chrome may be blocking site access. Open the extension’s Details page and check Site access. If the target website was not part of your original request, add it in a revision.

Open chrome://extensions, find the extension, and select the service worker error link to view the details. Reload once. If it returns, copy the error text and send it with the project ID; the exact message is necessary to identify the broken file or event.

Pin the extension and check its toolbar button first. Side panels may open from Chrome’s side-panel control, and context menus only appear on the page elements they were designed for. If the expected interface is still absent, describe exactly where it should appear in a revision.

State what happens now, what should happen instead, where it should work, and the action that triggers it. Example: “When I click Save in the popup, store the text and show it again when I reopen the popup.” Avoid replacing the entire request unless you truly want a different extension.

Small related changes can be combined. Test major features one at a time so you know which change caused a new problem. For unrelated features, make the highest-priority correction first.

Include the project ID, the exact steps you took, what you expected, what happened instead, the webpage where you tested, and the complete Chrome error text. A screenshot is helpful, but the written error message is even better.

Confirm you are signed into the account used at checkout, then refresh your account or project page. Do not purchase the same package again while the first payment is being checked. Contact us with the order number if the balance remains incorrect.

Use the password reset option on My Account. Make sure you use the same email address used during registration or checkout. If the reset email does not arrive, check spam before contacting support.

No. Google reviews extensions under its current technical and policy requirements. You are responsible for testing, accurate disclosures, requested permissions, privacy information, listing assets, and policy compliance. Use our publishing guide as a starting point.

Review the Refund and Returns Policy, then contact us with the email address used at checkout and the relevant order or project number.