Steps to reproduce
Describe what you opened, what you clicked or typed, and what happened next. Include the smallest sequence that causes the issue consistently.
Have questions, feedback, or suggestions? We'd love to hear from you! Reach out to us through any of the methods below.
Send a message directly from here for support, feedback, bug reports, or feature requests.
A clear report makes a technical problem easier to reproduce. Never send passwords, OAuth secrets, private repository content, session verification keys, or values from a .env file.
Describe what you opened, what you clicked or typed, and what happened next. Include the smallest sequence that causes the issue consistently.
Share the browser name, device type, and whether you were using the normal frontend workspace, collaboration, GitHub, publishing, or Node.js mode.
Copy the exact safe error message and line number. A screenshot can help, but remove personal information, repository secrets, and private chat before attaching it.
Use Support for a feature that is available but not behaving as documented. Check the complete help guide first; it covers files, previews, GitHub, Node.js, publishing, and collaboration.
Choose Bug Report when the same action produces an error or broken interface repeatedly. A focused sample project is more useful than a large unrelated project.
Explain the task you are trying to finish, who it helps, and how you expect the workflow to behave. That context is more actionable than only naming a button.
Read the privacy and data guide, then contact us if you need clarification about browser storage, connected services, cookies, publishing, or collaboration data.
Some questions arrive often enough to answer here. If yours is not covered, the form above reaches the same inbox.
Messages go straight to the support inbox and are usually answered within a couple of days. CodX Editor is built and maintained by one developer, so there is no on-call rota — a detailed bug report with steps to reproduce will always get a faster and more useful reply than a one-line message.
It is free to use, with no account required for the standard workspace and no paid tier. Running the site costs money, which is covered by advertising rather than by charging for the editor. There is no plan to put existing features behind a payment.
Almost certainly not, and it is better to be direct about why. Projects are stored in your own browser, not on a server, so there is no copy on our side to restore from. The saved-project library holds up to 24 entries and an autosaved recovery draft stays available for about seven days — if those are gone, clearing your browser data removed the only copy. For anything that would hurt to lose, use Download, ZIP All Projects, or push to GitHub.
Yes. You keep full ownership of the code and content you create, and nothing you write in the editor is claimed by CodX Editor. That is your work to sell, publish, or license as you choose. You are responsible for having the rights to anything you import, and the editor interface and application code themselves are proprietary and not open source.
Use the contact form with the topic set to Other, or email support@codxeditor.com directly, and please report it privately before disclosing it anywhere public. Include what you did, what you observed, and why you believe it is a problem. Do not include real credentials, live session verification keys, or another person's data as evidence — a description of the flaw is enough to act on.
Yes, from anyone, with no account needed. The requests that get built are the ones that explain the task being attempted rather than naming a button — what you were trying to finish, what got in the way, and what you expected to happen. Not every request can be built, and a request that is turned down still gets a reply explaining why.
Any current version of Chrome, Edge, Firefox, or Safari on desktop, and current mobile Chrome and Safari. Some features need more than the basics: the browser Node.js runtime relies on cross-origin isolation and SharedArrayBuffer, and writing an updated ZIP back to a file you selected depends on browser support for that permission. Where a feature is unavailable the editor says so instead of failing quietly.
Support covers CodX Editor itself — a feature not behaving as documented, an error in the interface, something in the help guide that is wrong or unclear. It does not extend to debugging your own project code or teaching a language, simply because there is one person answering. If the editor is reporting something that looks incorrect, that is a bug report and very much worth sending.