Text Editor
Text Editor

Free app for editing text files

Google Account
▾ ADVERTISEMENT ▾

Welcome to Text Editor

Text Editor is a free app for creating, opening, and editing text and code files on your computer and in Google Drive.

Loading...

How to use Text Editor

  1. Open a file from your computer or Google Drive using the File menu, or simply drag and drop a file onto the page. You can also open Gmail attachments with Text Editor, or start a fresh document with File > New.
  2. Edit the file in your browser. Syntax highlighting switches on automatically based on the file type, and the toolbar and menu bar put editing, formatting, and view options one click away.
  3. Save from the File menu or the toolbar. Files from your computer save back in place in Chromium browsers such as Chrome, Edge, and Opera. In Firefox and Safari, Save downloads a copy instead. Files from Google Drive save back to Drive in any supported browser.
  4. Leave autosave on (it is on by default), and Text Editor saves your work a few seconds after you stop typing, the way Google Docs does.

How Text Editor works

  • Text Editor is a pure JavaScript web app. File processing happens locally in your browser. Your files are never uploaded to a Text Editor server.
  • Text Editor opens plain text and code files: notes and documents like TXT and Markdown, data files like CSV, JSON, and XML, web files like HTML and CSS, and source code in languages such as Python, JavaScript, Java, and C++. Binary files are detected up front and refused, with the option to view them anyway. See the full list of supported file types.
  • Character encodings are detected automatically, and you can reopen a file with a different encoding at any time using Tools > Encoding.
  • Text Editor is built on proven open source components, including the Ace editor that powers many development tools on the web.
  • It works in current versions of Chrome, Microsoft Edge, Firefox, and Safari. Saving in place to files on your computer requires a Chromium browser. See browser support for details.

A tour of Text Editor's features

The quickest way to learn Text Editor is to open a file and look around. This section walks through the main surfaces of the editor and where its features live.

The toolbar and menu bar

The toolbar above the editor covers the actions you reach for most often. It holds Save, Undo and Redo, a font size stepper, toggles for line numbers, word wrap, and invisible characters like tabs and line endings, and code tools for commenting out lines, indenting and outdenting, and reformatting the document. When you edit Markdown, formatting buttons for bold, italic, underline, lists, headings, quotes, and code appear alongside them. Find, find and replace, and the command palette sit at the right edge.

The menu bar above it holds the complete command set in the File, Edit, View, Format, Tools, and Help menus, laid out the way you know from apps like Google Docs. The Tools menu adds a word count, autocomplete, and syntax checking. If you prefer the keyboard, the command palette runs any command by name, and the Help menu lists every keyboard shortcut. See also the keyboard shortcut FAQ.

Edit, Split, and Preview views

For supported formats, Text Editor offers three views from the View menu. Edit shows just the editor. Split shows the editor and a live preview side by side: the preview updates as you type and can scroll in step with the editor. Preview shows only the rendered result, which is ideal for reading. Text Editor previews Markdown, HTML (inside a security sandbox), CSV/TSV, XML, JSON, SVG, LaTeX, and RTF, and offers a clean reading view for plain text. For writing without distractions, full screen mode hides the surrounding app controls. Learn more in the preview FAQ.

Saving, autosave, and Google Drive

Text Editor saves the way a desktop editor does. When you save, your changes are written back to wherever the file lives: in place on your computer in Chromium browsers, or back to Google Drive in any supported browser. The File menu shows the commands that fit the current file, from Save as and Make a copy to moving a file's home between your computer and Drive.

Autosave is on by default: once a document has a writable home, edits flush to it automatically, and the save status in the app bar shows when everything is saved. Recovery drafts stored in your browser guard unsaved work against a closed tab or a crash. See autosave and recovery in the help center.

Files that live in Google Drive get their own File menu section with commands like Share, Move, and Version history. You can also install Text Editor in Google Drive so it appears in Drive's Open with menu. More in the Drive FAQ.

Themes, fonts, and keyboard modes

The theme chooser in the View menu previews themes live as you move through the list: nine light themes including TextMate, GitHub Light, and Solarized Light, and nine dark themes including Tomorrow Night, Monokai, Dracula, and Nord. Editor fonts include Roboto Mono, JetBrains Mono, and Fira Code alongside your system monospace fonts, with an adjustable size. And if your fingers already know another editor, the keyboard mode chooser in the Tools menu switches the entire keymap to Vim, Emacs, Sublime, or VS Code bindings. See themes and keyboard modes in the FAQ.

Printing

File > Print opens a print dialog with a preview of the result. Document text prints with options like margins and line numbers, and Markdown, CSV/TSV, XML, JSON, LaTeX, RTF, and plain text documents can print their rendered preview instead, so what you send to the printer matches what you see on screen. HTML and SVG files print as document text. Details in the printing help.

About plain text and text editors

Plain text is the simplest way a computer can store writing: a file that contains characters and nothing else: no fonts, no colors, no hidden layout data. That simplicity is why plain text has outlasted decades of file formats. It is small, fast, readable on any device, easy to compare and back up, and it will still open long after today's software is gone. A text editor is any program built for working with these files.

A brief history of text editors

The earliest editors worked one line at a time, because early terminals printed onto paper and there was no screen to redraw. Video terminals made full-screen editing possible, and two of the most influential editors of that era, vi and Emacs, appeared in the 1970s and are still in daily use today. Graphical desktops later put a simple editor on every computer. Windows Notepad has been quietly opening files since the 1980s. The newest chapter moves the editor into the browser, where there is nothing to install and your editor is wherever you are.

A text editor differs from a word processor in one essential way: a word processor embeds formatting into its files, while a text editor stores exactly the characters you type. That is why code, configuration, and data files are almost always edited as plain text.

Common plain text file formats

Many everyday formats are plain text underneath. Notes and READMEs are usually TXT or Markdown. Tabular data travels as CSV, a format so simple it has survived since the 1970s. Structured data and configuration use JSON, XML, or YAML. Web pages are HTML and CSS. Source code for programs written in Python, JavaScript, Java, C++, and hundreds of other languages is plain text, which editors display with syntax highlighting to make its structure easy to scan. Text Editor recognizes all of these, highlights them, and previews several of them.

Character encodings: from ASCII to UTF-8

A text file is ultimately just bytes, and a character encoding is the rulebook that turns those bytes into letters. For decades the dominant rulebook was ASCII, which covers 128 characters, enough for English and little else. Today's standard is Unicode, which assigns a number to more than 150,000 characters across the world's writing systems, most often stored as UTF-8. When a file was written with a different rulebook, its accents and symbols can appear garbled. Text Editor detects the encoding automatically and lets you reopen a file with another one from the Tools menu. See the text encoding help.

Markdown and lightweight markup

Markdown was created by John Gruber in 2004 with a simple goal: a way to write formatted documents in plain text that reads naturally even before it is rendered. Asterisks make emphasis, pound signs make headings, and dashes make lists. It became the everyday language of READMEs, documentation, and discussion forums, was standardized as CommonMark, and grew popular extensions like GitHub Flavored Markdown for tables and task lists. Text Editor gives Markdown special attention: formatting buttons on the toolbar, lists and headings from the Format menu, and a live preview that sits beside your text and updates as you type. Open a .md file and try it.

Common questions

A few quick answers from the FAQ:

For anything else, browse the FAQ and the help center, or write to us at info@texteditor.co.

Further reading

Text editors have a history nearly as old as computing itself, and an enormous family tree, from the line editors of the teletype era to the programmable environments many developers live in today. Wikipedia maintains both a list of text editors and a detailed comparison of text editors if you would like to see how deep the topic goes.

However you write, whether notes, code, data, or documentation, we hope Text Editor makes it a little easier.

Copyright © 2026 Text Editor by Visware