Feature

The live code editor for your training sessions

You type, the whole room follows line by line. Everyone has their own editor at the same time, runs their program in their browser, and you collect everybody's work at the end. Nothing to install, on your side or theirs.

Get started for free →

A shared code editor, with nothing to install

Getting a group to write code always starts with the same lost half hour: installing Python, sorting out a version, unblocking an antivirus, rescuing the one person whose editor will not start. The EduTools code editor removes that step — it lives in the browser, and your learners join with a room code or a QR code.

You open a session and type your example: it appears on everyone's screen as you go. Each participant also has their own editor and works in it when you say so — without losing sight of yours.

The code really runs, in the browser

An editor that runs nothing is only good for copying. Here the Run button actually executes the program: print, input, if, for, while, functions, lists and dictionaries. The console shows the output and asks the program's questions, like a real terminal.

Everything happens in the browser of whoever wrote the code. Nothing runs on our servers, and a learner's program reaches nothing beyond their own page. An endless loop — the beginner's mistake — is stopped on its own instead of freezing the machine.

Python, SQL, JavaScript, HTML and CSS

Four languages genuinely run. Python and JavaScript print their output in the console. SQL queries a real SQLite database, loaded in advance with customers, products and orders: your learners write SELECTs, joins and groupings, and read the result in columns. HTML and CSS are displayed instead: the page appears below the code.

For an HTML demonstration, your learners watch your page change while you edit the style — which beats any explanation.

PHP, Java, C, C++ and C# are offered too, with their syntax highlighting: they do not run in a browser, but your learners write them and you collect their files.

What you can do

Your code, live

What you type reaches every participant at each pause, with nothing to reload on their side.

👥

One editor per learner

Everyone works in their own copy, which starts from your example, and keeps yours displayed alongside — or hides it for more room.

▶️

Runs in the browser

print, input, conditions, loops and functions genuinely run — and SQL queries against a real database. Nothing to install.

🎨

HTML and CSS preview

The page is drawn below the code: ideal for showing what a CSS property does, live.

📥

You collect everything

Every participant's work is available from your back office, downloadable one by one or as a single archive.

🔒

Take back the room

One click puts everyone back in read-only and on your screen. Their copies are not lost: they return when you hand them back.

The code editor in pictures

A session from the trainer's side, the same from a learner's side, and an HTML page preview.

The session, trainer's side

The program runs in the console: the questions asked by input(), the answers typed in, then the result. The code reaches the room at every pause.

Two editors, one screen

Their copy on the left, where they write freely; yours on the right, live and read-only, hidden in one click when they want to focus.

The HTML and CSS preview

The page appears below the code, with its colours, spacing and shadows. Change a property, preview again, see the difference.

SQL, on a real database

SQLite runs in the browser, on a sample database loaded in advance. Results appear in columns, just like in a SQL client.

When to use it?

Getting a group to write code

A code session takes two minutes to prepare and runs with nothing installed, on your side or your learners'.

Tips

  • Prepare your example before the session, in a session with no room: it serves as a draft nobody can see.
  • An endless loop is stopped automatically — tell your learners, and they will dare to experiment more.
  • In HTML/CSS, change a colour then preview again: watching the page change beats a long explanation.
  • The editor covers the fundamentals. Tkinter, files and external libraries need an installed environment: plan for that in your course.

Frequently asked questions

Does anything need installing on the computers?
Nothing at all. The editor and the execution live in the browser. Your participants open a link or scan a QR code and are writing code within the minute — even on a machine locked down by an IT department.
Which languages are available?
Four languages run: Python and JavaScript with their output in a console, SQL against a provided SQLite database, HTML/CSS rendered as a page. Five more come with syntax highlighting only — PHP, Java, C, C++ and C# — so learners can write them and you collect the files. Every file carries the right extension: .py, .sql, .java…
Can we build graphical interfaces, read files, install libraries?
No, by design: the editor covers the fundamentals — output, input, conditions, loops, functions, lists, dictionaries, classes, plus math and random. Tkinter, file access, networking and libraries such as NumPy are not available. Those topics still need an installed environment.
What happens if a learner writes an endless loop?
The program is stopped automatically after a few seconds, with a message explaining why. It is the most common beginner's mistake, and it blocks neither their machine nor the session. A Stop button is also there at any time.
How do I collect everyone's code?
A page in your back office gathers the code produced, room by room. You read each participant's work, download it individually, or take the whole group as a single archive.
Is the code editor included in the free plan?
The free plan allows one code session, enough to try it with a real group. Paid plans lift that limit.

Also worth exploring

Ready to try?

Create your free account in minutes. No credit card, no install required for your participants.

Get started for free →