Open, fix and save config files, scripts, JSON, XML, YAML, SQL, CSV and logs, or a whole folder, in the editor core of VS Code: tabs, search across files, diff and formatters, all on your device
🔒 Your data stays in your browser: nothing you type or upload is sent to a server.
How it works
This is Monaco, the editor core that VS Code is built on, running inside the page and loaded only when you open this tool. Open one or many files, or a whole folder (in Chrome, Edge, Opera and Brave edits are saved straight back to the files; in Firefox and Safari "save" downloads the file and the folder can be exported as a ZIP). You get tabs, find and replace, search across every file of the folder, a command palette (F1), quick open (Ctrl+P), split view, diff against the saved version or another file, and formatting for JSON, XML, YAML, SQL, HTML, CSS and JavaScript. JSON, YAML and XML are checked while you type, with the error marked on its line. Nothing is uploaded: files are read and written only on your device.
Common questions
Can I edit a file on my computer and save it back to the same file?
In Chrome, Edge, Opera and Brave, yes: the browser File System Access API lets this page write to a file or folder you picked, after you allow it, and Ctrl+S saves in place. Firefox and Safari do not offer that API, so there the file is opened from a normal file picker (or by dropping it) and "save" downloads a new copy that you move over the original. The editor tells you which mode you are in.
Is this really the VS Code editor? What is missing compared with VS Code?
The text editor is Monaco, the same code that powers VS Code: multi-cursor, find and replace with regular expressions, folding, minimap, bracket matching, IntelliSense for JavaScript, TypeScript, JSON, HTML and CSS, the F1 command palette and a diff editor. What is not here is everything around it: extensions, a terminal, a debugger, Git, and project-aware features such as IntelliSense across files with node_modules. Monaco's own menus and command names are in English.
Are my files uploaded anywhere? What happens with large or binary files?
No file, folder or text leaves your device: the editor and its language services run in your browser and there is no server side. Files above 5 MB open as read-only plain text so the page stays responsive (you can allow editing), files above 100 MB are refused, and files with binary content open in a read-only hex view with a warning. Your open tabs and unsaved changes are kept only in this browser (IndexedDB and local storage), so you can restore them after a crash; closing the tab asks first if anything is unsaved.
Does saving change the encoding or the line endings of my file?
No, unless you ask. The editor detects UTF-8 (with or without BOM), UTF-16 LE/BE and Windows-1252, and whether lines end with LF, CRLF or CR, shows both in the status bar and writes the file back the same way, byte for byte where you did not edit. You can change either from the status bar; if you save to Windows-1252 text it cannot represent, those characters are written as "?" and you are warned first. A file whose line endings are mixed is saved with the dominant one.