SQL Code Editor is a phone workspace for writing, formatting, and running SQL on SQLite databases that remain on the device. You type a script, choose a database, and run the statement at the cursor or the whole script. A .sql file stores only the text. The database file stores the tables and the rows. They stay separate, so a script can be edited on its own.
The editor shows syntax colors and line numbers, and it can keep more than one script open in tabs. Find and replace can match case, move to the next or previous hit, or replace every hit. You can jump to a line number, turn word wrap on or off, cut, copy, paste, select all, and duplicate a selection. Snippets insert common SQL patterns. Formatting can place keywords in upper case, lower case, or leave them as written, and it can break the text before clauses such as SELECT, FROM, WHERE, and ORDER BY.
Run sends the statement at the cursor to the selected SQLite database. Run script sends the full editor. Run selection sends only the highlighted part. When a statement can change or remove data, SQL Code Editor asks you to confirm before it runs. An empty editor does not run. While a query is in progress, the next run waits. A successful query shows the result under the editor. The grid shows the first 1000 rows. Export to CSV or JSON can write the full result when the statement can be run once more.
You can create a database, import a SQLite file, back it up, and restore it on this phone. The browser lists tables and views, shows the schema, primary keys, foreign keys, and indexes. You can search a table, sort a column, filter rows, insert a row, edit a row, or delete a row. An empty field is stored as NULL. Views can be browsed here and changed with SQL in the editor. Dropping a table or deleting a row asks for confirmation, because that action cannot be undone.
New SQL files are saved under Internal storage, then Documents, then SQL Code Editor. Save updates the current file. Save as stores a copy in another place. From a file manager, Downloads, or another app, you can open a .sql or .txt file and choose SQL Code Editor. Share sends the current document to another app. The home screen lists recent files, recent databases, and saved queries, and you can search that recent work.
Query history keeps statements on this device when the history setting is on. Each item can be copied, run once more, saved under a name, or deleted. Deleting a history item does not delete the original SQL file. History can be turned off. Saved queries stay in their own list until you delete them.
Settings cover a light theme, a dark theme, or the system theme, plus editor font size, tab width, autosave for open files, keyword style, and read-only choices. The guide inside SQL Code Editor explains the difference between a script and a database, where files are saved, and how run, save, and history work. Drafts of unsaved documents stay on the device. If you leave with unsaved changes, you are asked before those changes are discarded.
An internet connection is required before the main screen opens. The check uses Wi-Fi or mobile data and does not upload your scripts, drafts, query text, or database files. If the connection drops after the editor is already open, you can still save a draft on the device. SQL Code Editor does not ask you to create an account.
SQL Code Editor is meant for people who write SQL on a phone: learners practicing SELECT, INSERT, UPDATE, DELETE, and CREATE TABLE, and developers who want a SQLite file beside the script. Statements run with SQLite on the device. It does not provide every feature of MySQL, PostgreSQL, or SQL Server, and it does not sign in to those servers. Use it only with files and databases you are allowed to open.
Open SQL Code Editor when you want the script, the result grid, and the SQLite database together on your phone, with history you can revisit and files you can save, share, and open later.
SQL Code Editor writes, formats, and runs SQLite scripts stored on your phone.