# How to put a script on the Cronus Zen (Zen Studio and Zen Studio Live)

> To put a script on the Cronus Zen, connect its PROG port to a computer, open Zen Studio Live in Chrome, send the script to a slot and click Program.

- Canonical: https://cronuswiki.com/docs/how-to-put-a-script-on-cronus-zen
- Site: Cronus Wiki (https://cronuswiki.com/)
- Author: Cronus Wiki Editorial (https://cronuswiki.com/authors/editorial)
- Section: Setup
- Published: 2026-09-21 · Updated: 2026-10-07
- Tags: zen studio, zen studio live, gpc, slots, programming

---

To put a script on the Cronus Zen, connect the Zen's PROG USB port to your computer with a data cable, open Zen Studio Live in Chrome and click Connect Device, then send the script to a memory slot and click Program. That is the route Cronus's current guide starts with; it calls Zen Studio Live the new browser-based version of Zen Studio, and its Downloads page lists no desktop app. The desktop Windows app, Zen Studio, still works, and Cronus's older guide files it under "ZEN STUDIO (LEGACY)" in its menu. This page covers both routes, what Build and Run does compared with programming a slot, how to replace or erase a slot, and the messages you can hit on the way.

## Zen Studio Live or Zen Studio (legacy)

| | Zen Studio Live (browser) | Zen Studio (desktop, legacy) |
| --- | --- | --- |
| Runs on | Chrome (Cronus's recommendation) on Windows, macOS or Linux; not iOS | Windows 10 or 11 |
| Install | None; it is a web page | An installer |
| Newest version Cronus lists, 7 October 2026 | 1.0.9, released 8 September 2026 (current guide's changelog) | 1.6.1 Build 82 (older guide) |
| Connecting | Connect Device, then choose Cronus Bridge | Automatic over PROG; Device panel, Find Device if it is not seen |
| Where slots are filled | Scripts Library (Send to Slot) or Device Slots (GamePacks), then Home, Program, Program Slots | Programmer panel: drag onto a memory slot, then Program Device |
| Temporary test without a slot | Compiler, Build and Run (F5) | Compiler, Build and Run (F5) |
| Firmware updates | Update Firmware, bottom-left corner | Tools, Firmware Update |

Sources: Cronus's [Start Zen Studio Live](https://guide.cronuszen.com/quick-start-and-downloads/step-1-start-zen-studio-live) and [All-in-One setup](https://guide.cronuszen.com/cronus-zen-guide/all-in-one-easy-setup) pages, its [Downloads](https://guide.cronuszen.com/quick-start-and-downloads/downloads) page and [2026 changelog](https://guide.cronuszen.com/changelogs/changelog-26), and the older guide's [Zen Studio](https://guide.cronus.support/zen-studio) and [Step 2](https://guide.cronus.support/step2-install-zen-studio) pages.

Cronus says Firefox and Safari will likely not work for its browser tools. On the desktop app, Cronus's [Zen Studio Errors](https://guide.cronus.support/zen-studio-errors) page says that if version 1.5.0 Build 24 shows a Software Update window you must click Cancel, because a bug in that build stops it installing, and that you should uninstall the old version before installing 1.6.1 Build 82.

## What you need

| Item | Detail |
| --- | --- |
| A **data** USB cable | From the Zen's **PROG** port to the computer. Cronus's current guide says a charge-only cable lights the Zen up but leaves it invisible to the computer |
| The script | An entry in the Scripts Library, or a .gpc file; GPC is plain text |
| Chrome, or Windows with Zen Studio | Either tool above |
| A registered Zen, for the library | Cronus's GPC library is open only to registered Zens. Registration is step 3 of Cronus's [quick start](https://guide.cronus.support/quick-start) and links the Zen's serial number to your Cronus Community account. A used Zen can still be registered to its previous owner; Cronus's Step 2 page covers that case |
| Not needed | The console or a controller; programming works with the Zen connected to the computer alone |

## Step by step in Zen Studio Live

1. **Connect PROG to the computer** with a data cable. Open Zen Studio Live in Chrome (`zenstudio.collectivemindsstore.com`, linked from Cronus's guide), click **Connect Device**, choose **Cronus Bridge** in the window Chrome opens, and click **Connect**. Chrome asks for this permission once per browser. If Cronus Bridge is not in the list, Cronus says it is almost always the cable: try a different data cable, then unplug the Zen, plug it back in and click Connect Device again.
2. **Choose what goes in a slot.** For a library script, open the **Scripts Library** icon on the left sidebar, press **Send to Slot** and choose a slot. For a GamePack, open **Device Slots**, press **Send** on the pack and choose a slot; a settings window usually opens, and Cronus notes you can press Save and adjust the settings on the Zen's OLED instead. For a script of your own, open the .gpc file with the **Open File** icon at the top left; the **Editor** icon shows the code. Cronus's walkthrough does not spell out the slot step for a file of your own; the desktop Programmer panel below documents it, and in either tool Build and Run (below) tests your file without using a slot.
3. **Program.** Press the **Home** icon, click **Program**, check the overview of what is going into each slot, and click **Program Slots**. It takes a few seconds and ends with a green **Programming complete** message at the bottom right. Zen Studio Live blocks closing or reloading the page while it programs; leave the cable alone too.
4. **Move to the console.** Unplug PROG; Cronus says it must be disconnected before you start a game. Connect the Zen's CONSOLE/PC port to the console, and press **P1**, the Memory Slot button, until the OLED shows the slot you programmed.

## Step by step in Zen Studio (desktop, legacy)

1. **Connect PROG to the PC**, not CONSOLE/PC. The left end of Zen Studio's status bar shows whether the Zen is connected and its firmware version. If Zen Studio says **Device Not Connected**, Cronus puts it down to a poor connection or a faulty cable; with a good cable, use **Device panel, Find Device**.
2. **Open the script** with **File, Open** (Ctrl+O). It opens in its own Compiler tab.
3. **Compile** with **Compile (F7)**. The output lists errors, warnings, bytecode size and the share of slot memory used. Cronus's [Compiler page](https://guide.cronus.support/zen-studio-working-panel-compiler) says warnings should be treated as errors, because they can cause runtime problems even when compilation succeeds.
4. **Program a slot** in the **Programmer** panel. Any script open in the Compiler appears under **GPC Scripts**; drag it onto a memory slot, then click **Program Device**, which writes every configured slot to the Zen ([Programmer page](https://guide.cronus.support/zen-studio-working-panel-programmer)).
5. **Move to the console** as in step 4 above.

## Build and Run versus programming a slot

**Build and Run (F5)** compiles the active script and loads it straight into the Zen's RAM; it runs immediately without programming a memory slot. Device Monitor shows such a test as slot 10. Cronus's GPC guide describes it as a temporary test build and says to program a memory slot only when you want to keep the script on the Zen after the session. Use Build and Run to try a script, and Program when you want it to stay.

## Replacing or erasing a slot

| You want to | Do this |
| --- | --- |
| Replace a script | Put the new script in the same slot and program again |
| Clear one slot (desktop) | Drag the slot to the trash icon, then click Program Device to confirm |
| Clear every slot, keep settings | Device panel, **Erase Memory Slots**: Cronus says it erases all memory slots without affecting any other option |
| Wipe slots and settings | Device panel, **Factory Reset**: resets every option to factory defaults and erases the slots |
| See how full the Zen is | Device panel, **Zen Flash**: the flash memory used by what is in the slots |

The Device panel also holds **Find Device**, **Reset Device** (restarts the Zen without unplugging it) and **Clear BT Devices** ([Device page](https://guide.cronus.support/zen-studio-working-panel-device)).

## What each message means

| Message | Where | Cause | Fix |
| --- | --- | --- | --- |
| Device Not Connected | Status bar, both tools | Poor connection or faulty USB cable | Data cable in PROG; Find Device (desktop) or Connect Device (Live) |
| Cronus Bridge missing from the list | Zen Studio Live, Connect Device | Charge-only cable, or the Zen needs replugging | Another data cable; replug; Connect Device again |
| Device Disconnected | Desktop | Cable not in PROG, faulty cable, or a PC port without enough power | Data cable in PROG; another port or a powered hub |
| Device Connected But Not Responding | Desktop | Zen Studio lost its pairing, or the firmware is too old | Find Device; replug PROG; update the firmware |
| Firmware Version Incompatible | Desktop | The firmware or Zen Studio is out of date | Update the firmware, then reopen Zen Studio |
| Programming Error | Desktop | Faulty cable, corrupt Zen Studio files, or a script with outdated code | Tools, Reset Zen Studio; another cable |
| Stuck on Programming | Desktop | A known issue, per Cronus | Replug PROG; Tools, Reset Zen Studio; Find Device |
| A compiler error with a line number | Compiler, both tools | A mistake in the text, a pasted file cut short, or a function the firmware lacks | Fix the first message from the top first; open the .gpc file instead of pasting |
| A script larger than a slot | Compiler | Bytecode above the 32 KB a slot holds | A lighter build from the author |

The first seven rows use Cronus's wording from its [Step 2](https://guide.cronus.support/step2-install-zen-studio), [Zen Studio Errors](https://guide.cronus.support/zen-studio-errors) and [Start Zen Studio Live](https://guide.cronuszen.com/quick-start-and-downloads/step-1-start-zen-studio-live) pages. The last two describe the case; compiler wording differs between the tools and between versions. Tools, Reset Zen Studio erases Zen Studio's backups, settings and stored files on the computer, but nothing on the Zen. [Zen Studio errors](/docs/zen-studio-errors) lists the rest.

## The three places it goes wrong

**The cable.** A charge-only cable lights the Zen while leaving it invisible to the computer. Cronus's quick test: connect your phone to the computer with the same cable; if the phone's files show up, it is a data cable. Change the cable before you change anything else. [Cronus Zen not detected](/docs/cronus-zen-not-detected) is the full diagnostic if a new cable does not fix it.

**The port.** PROG is for Zen Studio and Zen Studio Live. CONSOLE/PC, which Cronus's current guide calls the top port, is for the console and for firmware updates in bootloader mode. A cable in the wrong one gives you a device that is clearly alive and not talking. [Ports and cables](/docs/cronus-zen-ports-and-cables).

**The firmware.** Cronus links stack and bytecode errors to a GamePack or script designed for a different firmware. Desktop Zen Studio shows the firmware version in its status bar, and Zen Studio Live flags newer firmware in its connected-device area; compare it with the version the script's author names. [Firmware: update, downgrade, recovery](/docs/cronus-zen-firmware-update-downgrade-recovery).

## Programming from macOS

Zen Studio Live in Chrome is the route on a Mac; Cronus lists macOS as supported. The desktop app is Windows-only. Cronus's older pages describe running it under Windows through Boot Camp on Intel Macs, and for Apple-silicon Macs they name Parallels on one page and VMware Fusion Technology Preview 2023 on the error pages, adding that Cronus does not offer Mac support and has not tested that setup. With Zen Studio Live, none of that is needed.

## What "programmed" actually means

Compiling turns the GPC text into bytecode the Zen's firmware can run. Programming writes that bytecode into one of the Zen's eight memory slots, each 32 KB ([Working Panels](https://guide.cronus.support/working-panels)). It stays there through power cycles, console changes and cable swaps until you replace it, erase the slots or reset the device. A Build and Run test does not. [Script slots and memory](/docs/cronus-zen-script-slots-and-memory) explains what persists, what a hard reset clears, and why some scripts forget their settings.

## Quick reference

| Symptom | Most likely cause | First fix |
| --- | --- | --- |
| Zen lit, the tool sees nothing | Charge-only cable, or cable in CONSOLE/PC | Data cable in PROG |
| Cronus Bridge not in Chrome's list | Cable | Another data cable; replug |
| Compile fails on the last line | Final line lost in pasting | Open the .gpc file instead of pasting |
| Compile fails on an unknown function | The script targets other firmware | Update the firmware, or ask the author |
| Script gone after a power cycle | It was only run with Build and Run, or the write was interrupted | Program the slot; wait for the confirmation |
| Script runs but does nothing | Wrong slot selected, or it needs an activation combo | Read the OLED; read the script's notes |
| Works on the PC, not on the console | No slot selected, or a script for another console | Press P1; check the script's target |

## FAQ

**Do I need Zen Studio installed to load a script?**

No. Zen Studio Live runs in Chrome with nothing to install, and Cronus's current guide, which calls it the new browser-based version of Zen Studio, starts setup there. The desktop Zen Studio is Windows-only, and Cronus's older guide files it under Zen Studio (Legacy).

**Where do I get a .gpc file?**

From the script's author, or from Cronus's GPC library of free community scripts, which needs a registered Zen. Paid scripts arrive as a download from the seller. This site does not host scripts.

**Can I put more than one script on the Zen?**

Yes. Cronus lists eight memory slots of 32 KB each, and each holds one script, GamePack or remapper profile. Move between them with P1, the Memory Slot button on the Zen.

**Why does the script disappear after a reboot?**

A script tested with Build and Run is loaded into the Zen's RAM and never written to a slot, so it is not kept. Only Program writes a slot. If a programmed slot comes back empty, the write was interrupted: program it again and wait for the confirmation.

**Do I need the console connected to load a script?**

No. Programming happens over the PROG port from the computer. Cronus's own setup walkthrough programs the slots before the Zen is connected to a console.

**Can I load a script from my phone?**

Partly. With the Zen Link module, Cronus says you can install and configure GamePacks from a smartphone over Wi-Fi. For your own scripts you need a computer: Zen Studio Live in Chrome on Windows, macOS or Linux. Cronus says iOS is not supported.