Need help with CQ-editor?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

239 Stars 44 Forks Apache License 2.0 526 Commits 84 Opened issues


CadQuery GUI editor based on PyQT

Services available


Need anything else?

Contributors list

CadQuery editor

Build status codecov Build Status DOI

CadQuery GUI editor based on PyQT supports Linux, Windows and Mac.

Screenshot Screenshot Screenshot

Notable features

  • OCCT based
  • Graphical debugger for CadQuery scripts
    • Step through script and watch how your model changes
  • CadQuery object stack inspector
    • Visual inspection of current workplane and selected items
    • Insight into evolution of the model
  • Export to various formats
    • STL
    • STEP

Installation - Pre-Built Packages (Recommended)

Release Packages

Stable release builds which do not require Anaconda are attached to the latest release. Download the zip file for your operating system, extract it, and run the CQ-editor script for your OS (CQ-editor.cmd for Windows, for Linux and MacOS). On Windows you should be able to simply double-click on CQ-editor.cmd. On Linux and MacOS you may need to make the script executable with

chmod +x
and run the script from the command line. The script contains an environment variable export that may be required to get CQ-editor to launch correctly on MacOS Big Sur, so it is better to use the script than to launch CQ-editor directly.

Development Packages

Development builds are also available, but can be unstable and should be used at your own risk. Click on the newest build with a green checkmark here, wait for the Artifacts section at the bottom of the page to load, and then click on the appropriate download for your operating system. Extract the archive file and run the shell (Linux/MacOS) or cmd (Windows) script in the root CQ-editor directory. The CQ-editor window should launch.

Installation (Anaconda)

Use conda to install:

conda install -c cadquery -c conda-forge cq-editor=master
and then simply type
to run it. This installs the latest version built directly from the HEAD of this repository.

Alternatively clone this git repository and set up the following conda environment:

conda env create -f cqgui_env.yml -n cqgui
conda activate cqgui

On some linux distributions (e.g.

Ubuntu 18.04
) it might be necessary to install additonal packages:
sudo apt install libglu1-mesa libgl1-mesa-dri mesa-common-dev libglu1-mesa-dev
On Fedora 29 the packages can be installed as follows:
dnf install -y mesa-libGLU mesa-libGL mesa-libGLU-devel


Showing Objects

By default, CQ-editor will display a 3D representation of all

objects in a script with a default color and alpha (transparency). To have more control over what is shown, and what the color and alpha settings are, the
method can be used.
tells CQ-editor to explicity display an object, and accepts the
parameter. The
parameter is a dictionary of rendering options named
is scaled between 0.0 and 1.0, with 0.0 being completely opaque and 1.0 being completely transparent. The color is set using R (red), G (green) and B (blue) values, and each one is scaled from 0 to 255. Either option or both can be omitted.
show_object(result, options={"alpha":0.5, "color": (64, 164, 223)})

Note that

works for
objects too. In order to display objects from the embedded Python console use

Rotate, Pan and Zoom the 3D View

The following mouse controls can be used to alter the view of the 3D object, and should be familiar to CAD users, even if the mouse buttons used may differ.

  • Left Mouse Button + Drag = Rotate
  • Middle Mouse Button + Drag = Pan
  • Right Mouse Button + Drag = Zoom
  • Mouse Wheel = Zoom

Debugging Objects

There are multiple menu options to help in debugging a CadQuery script. They are included in the

menu, with corresponding buttons in the toolbar. Below is a listing of what each menu item does.
  • Debug
    (Ctrl + F5) - Instead of running the script completely through as with the
    item, it begins executing the script but stops at the first non-empty line, waiting for the user to continue execution manually.
  • Step
    (Ctrl + F10) - Will move execution of the script to the next non-empty line.
  • Step in
    (Ctrl + F11) - Will follow the flow of execution to the inside of a user-created function defined within the script.
  • Continue
    (Ctrl + F12) - Completes execution of the script, starting from the current line that is being debugged.

It is also possible to do visual debugging of objects. This is possible by using the

function to display an object instead of
. An alternative method for the following code snippet is shown below for highlighting a specific face, but it demonstrates one use of
. ```python import cadquery as cq

result = cq.Workplane().box(10, 10, 10)

highlight = result.faces('>Z')

show_object(result, name='box') debug(highlight) ``

Objects displayed with
debug()` are colored in red and have their alpha set so they are semi-transparent. This can be useful for checking for interference, clearance, or whether the expected face is being selected, as in the code above.

Console Logging

Python's standard

function will not output to the CQ-editor GUI, and
should be used instead.
will output the provided text to the Log viewer panel, providing another way to debug CadQuery scripts. If you started CQ-editor from the command line, the
function will output text back to it.

Using an External Code Editor

Some users prefer to use an external code editor instead of the built-in Spyder-based editor that comes stock with CQ-editor. The steps below should allow CQ-editor to work alongside most text editors.

  1. Open the Preferences dialog by clicking
  2. Make sure that
    Code Editor
    is selected in the left pane.
  3. Check
    in the right pane.
  4. If CQ-editor is not catching the saves from your external editor, increasing
    Autoreload delay
    in the right pane may help. This issue has been reported when using vim or emacs.

Exporting an Object

Any object can be exported to either STEP or STL format. The steps for doing so are listed below.

  1. Highlight the object to be exported in the Objects panel.
  2. Click either
    Export as STL
    Export as STEP
    from the
    menu, depending on which file format you want to export. Both of these options will be disabled if an object is not selected in the Objects panel.

Clicking either Export item will present a file dialog that allows the file name ad location of the export file to be set.

Displaying All Wires for Debugging

NOTE: This is intended for debugging purposes, and if not removed, could interfere with the execution of your model in some cases.


is a quick way to combine all wires so that they will display together in CQ-editor's viewer. In the following code, it is used to make sure that both rects are displayed. This technique can make it easier to debug in-progress 2D sketches.
import cadquery as cq
res = cq.Workplane().rect(1,1).rect(3,3).consolidateWires()

Highlighting a Specific Face

Highlighting a specific face in a different color can be useful when debugging, or when trying to learn CadQuery selectors. The following code creates a separate, highlighted object to show the selected face in red. This is an alternative to using a

object, and in most cases
will provide the same result with less code. However, this method will allow the color and alpha of the highlight object to be customized.
import cadquery as cq

result = cq.Workplane().box(10, 10, 10)

highlight = result.faces('>Z')

show_object(result) show_object(highlight,'highlight',options=dict(alpha=0.1,color=(1.,0,0)))

Naming an Object

By default, objects have a randomly generated ID in the object inspector. However, it can be useful to name objects so that it is easier to identify them. The

parameter of
can be used to do this.
import cadquery as cq

result = cq.Workplane().box(10, 10, 10)

show_object(result, name='box')

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.