It is a browser-based development workspace for HTML, CSS, JavaScript, JSON, environment files, and Node.js projects. Instead of treating code as a disposable snippet, it gives you files, tools, previews, sessions, and ways to move the project elsewhere.
Create, rename, upload, download, and switch between multiple project files.
Use live preview, manual refresh, HTML inspection, console output, and error navigation.
Share a live session with roles, chat, custom cursors, waiting rooms, and access controls.
Save locally, export a project, connect GitHub, or publish a result when it is ready.
The workspace keeps the common web-development loop visible and close together.
Start a project and add the files it actually needs.
Use suggestions, Emmet, syntax colors, and diagnostics.
Preview frontend work or start a Node.js server.
Collaborate, export, publish, or update GitHub.
CodX Editor is designed like a collaborative project room, not only a quick snippet runner.
Hosts and co-hosts can manage a waiting room, roles, chat, editing, feature access, file visibility, user names, and whether participants may rename themselves.
Switch into a terminal-driven workspace, install dependencies, start a server, and open the detected local port without preparing a separate local environment first.
Use Emmet expansion, remembered classes and IDs, file-aware suggestions, syntax highlighting, and line-focused diagnostics.
Refresh results, inspect highlighted HTML, use fullscreen, adjust zoom, and connect console errors back to project lines.
Sign in through GitHub OAuth, browse repositories, create or upload files, and commit project updates from a connected session.
Your path is not limited to one page. Save locally, import files, download the project, connect a repository, or publish a link.
Browse Font Awesome code, apply Google Fonts with weight and spacing controls, and begin with project templates.
Use themes, editor fonts, keyboard shortcuts, Zen mode, and an editor-focused mobile layout when screen space is limited.
CodX Editor is most useful when setup should not get in the way of writing, seeing, explaining, or sharing code.
Learn how HTML, CSS, and JavaScript files work together while seeing changes quickly.
Practice, complete assignments, and continue from a browser on shared or personal computers.
Demonstrate concepts and invite learners into a controlled session without a long installation lesson.
Prototype an interface, reproduce a bug, test a package, or share a working example quickly.
A browser workspace is valuable, but it should not pretend to replace every production tool.
CodX Editor is made and maintained by a single self-taught developer. There is no team, no company, and no QA department.
The work before this one happened in VS Code, which is an excellent editor and was never the problem. The problem was everything around it. A new machine meant a fresh install and a fresh set of settings. A borrowed laptop meant nothing was set up at all. And a project living on one computer was, in practice, a project you could only work on at that computer.
Two things were missing: start writing code with zero setup, and reach the same project from whatever device you happen to be holding. Plenty of browser editors solve the first. Fewer treat the second as anything more than a copy-and-paste problem.
So this was built to do both. Everything about the design follows from those two requirements — no installation, no account needed to start, projects that are yours to move rather than ours to hold, and a way to carry a real multi-file project between devices without emailing yourself a ZIP.
Open the address and start typing. No download, no extensions to choose, no account, no configuration step between having an idea and writing the first line of it.
A Sync Key keeps one saved project current across several devices. The project is encrypted in your browser before it is uploaded, so the key is what unlocks it — and if the same project is edited in two places, you are asked which version to keep rather than one silently winning.
There is no paid tier and no plan to introduce one. Hosting is covered by advertising, which is why ads appear on the site pages — and why they never appear on projects that people publish.
Started within the past year and added to steadily since. Each piece was built because the one before it made it necessary.
The foundation, and the reason for everything after it. A single box for HTML, CSS and JavaScript is fine for a snippet, but a real project has files that reference each other. Getting this right first meant every later feature had something worth operating on.
Shared sessions with a waiting room, host and co-host roles, permissions, chat and pair tools. Once a project could hold several files, sharing it with another person became a question of who is allowed to change what — not just who can see the screen.
A public address for a finished project, with a verification key for updating it later and a version history so a replaced link can be reviewed or restored. Collaboration solved working together; publishing solved showing the result to somebody who was never in the room.
Sign-in through GitHub OAuth, with repository browsing and commits from a connected session — and deliberately no pasting of personal access tokens. This is the exit route: work that starts here does not have to stay here.
A terminal, npm packages and a development server running inside the tab, with the detected port opening straight into a preview. The most technically demanding piece by a distance, and the one that forced a rethink of how the rest of the site handles security headers.
Write-ups of problems met while building the editor, published after they were solved rather than summarised later. Several of them exist because the fix was not obvious and nothing online described the behaviour clearly.
Intentions rather than promises. One developer means an honest roadmap has no dates on it.
Open the starter project, change a file, inspect the preview, and explore the collaboration and project tools at your own pace.