Running the Stupid Cricut Software on Linux | Arthur Pizza

arthur.pizza
×
Home
About
Mastodon
PeerTube
YouTube
Patreon

arthur.pizza

Running the Stupid Cricut Software on Linux

December 29, 2025

•

3 min read

Why The Hell Would You do This?
I’m more than happy building vector designs in Inkscape. It’s the most proficient vector designer app that is free, open source, and runs natively under Linux. However, simply having a quality SVG is only part of the process when it comes to using a plotter like the Cricut.
On my own, I would not recommend the Cricut brand, but this is a machine that was bought years ago, and I want to get the most usage out of it.
How to Install Cricut Design Space
As far as I can tell, almost everything works in the Cricut Design Space application under Linux. The only bug I’ve noticed is the application becomes invisible when going full screen. This could easily be a Wayland bug too. I have no idea. Ideally, Cricut could Easily make a Linux Application with WINE. I could see this as a Flatpak install. I understand why they don’t, as that comes with the expectation of support, and supporting another operating system costs money.
This is a multistep process that you only really have to do once. Because of the complexity, I decided to lay out the instructions, along with the ‘why’ of the situation. The more you understand how it works, the more armed you are if anything goes wrong.
Getting the Software
I HIGHTLY recommend grabbing a fresh build of WINE. I’m a Debian user, so depending on the build of Linux you’re using it might vary, but I start on the Wine HQ Git. I know a lot of people might want to run a platform like Wine Bottles, but in my experience a more granular project like this is just easier under regular WINE.
OS Detection on the Website

When you visit the Design Space Download Page, it seems that the developer chose to use OS detection on the website. If it sees your user agent listed as Linux, for some weird reason it defaults to Mac. Logically, it would make more sense to default to the Windows build, but I think there was some corner cutting on this.
I recommend the open source UserAgent Switcher for this, as it has a build for Firefox and Chromium based browsers. (And of course, is free and open source.) After setting to “Windows 10” mode and refreshing the page:

Installing the Software
As of this tutorial, the latest build of Design Space is CricutDesignSpace-Install-v9.47.92.exe.
Make sure you’ve setup your install of WINE first. run winecfg and make sure everything is working.
wine CricutDesignSpace-Install-v9.47.92.exe
This will launch the installer. Just install like you normally would under Windows.
Logging in, the Stupid Parts…
First we need to find the binary with the where command. Here’s how it looked on my machine.
where cricut
cricut: aliased to wine '/home/art/.wine/drive_c/users/art/AppData/Local/Programs/Cricut Design Space/Cricut Design Space.exe'
Then we need to open two terminals (or two sessions, I use tmux for that).
Terminal #1
wine Cricut\ Design\ Space.exe
This will show the login panel and will want to launch your default browser. On my machine, that’s my native Firefox. Login there, and you’ll see a url asking for the Cricut software. Because your native browser and the wine wrapped cricut software can’t see each other, you gotta extract the part of the URL that features code=. In the second terminal:
Terminal #2
wine Cricut\ Design\ Space.exe "cricut://?code=XXXXXXXXXXXXXXXXXXX
You should be logged in!

Now you can start uploading your designs and colaborating with other through their locked down, proprietary platform. You can even waste money on stock images.

© arthur.pizzaCreative Commons CCSA

Running the Cricut Software on Linux: A Detailed Guide

This document details the process of running the Cricut Design Space software on a Linux operating system, primarily focusing on a user’s personal experience and troubleshooting methods. The author, Arthur Pizza, encountered challenges related to the software’s default behavior and provided a step-by-step guide for successful installation and operation, driven by a desire to utilize a previously acquired Cricut machine. The primary motivation for this endeavor stemmed from a dissatisfaction with the Cricut brand and a commitment to maximize the utility of their equipment.

The primary difficulty identified was the software’s initial OS detection, which defaults to the macOS build despite the user’s Linux environment. This necessitates the use of a third-party solution – the open-source UserAgent Switcher – to force a Windows 10 emulation. The author highlights the potential for corner-cutting in development, suggesting a more logical default setting.

The installation process itself is a multi-stage operation, recommended for initial execution only due to its complexity. The author stresses the importance of a properly configured WINE environment, including the execution of `winecfg` to ensure compatibility. The installation involves running the `CricutDesignSpace-Install-v9.47.92.exe` installer, mirroring a typical Windows installation procedure.

Subsequently, the operation relies on a dual-terminal approach. The first terminal executes `wine Cricut Design Space.exe`, triggering the login panel and launching the default web browser. This terminal is crucial for initiating the login process within the software’s browser-based interface. The second terminal employs the same command, but strategically incorporates the URL string `cricut://?code=XXXXXXXXXXXXXXXXXXX` to bypass the typical interaction between the WINE-wrapped application and the default browser. This technique allows the software to recognize and process the code parameter, effectively completing the login.

The author emphasizes the need for a deliberate approach, specifying the use of `where cricut` to identify the correct application path. Furthermore, the author cautions against assuming a seamless integration between the WINE environment and the native browser, illustrating the necessity of manually extracting the required URL component. This process essentially circumvents the software’s inherent limitations and replicates a functional login experience.

The document concludes with a pragmatic assessment of the Cricut platform itself, noting the potential for expenditure on stock images. This final observation underscores the user's perspective, driven by the desire to effectively utilize the machine regardless of the limitations imposed by its proprietary ecosystem. The author’s detailed account provides a practical, albeit somewhat convoluted, guide for individuals seeking to operate Cricut Design Space on a Linux system, highlighting the need for careful configuration, strategic command execution, and an understanding of the software's inherent limitations.