cables is under heavy development.
There might be one or another bug, please let us know about it!
cables DocumentationHow To UseWorking with filesKeyboard ShortcutsUser Interface WalkthroughBeginner TutorialBeginner 1: Drawing A CircleBeginner 2: TransformationsBeginner 3: ColorMore TransformationsIntermediateImage CompositionsPost-Processing 3D ScenesCommunicationcables APIExporting And EmbeddingHow to serve files externally and fix CORS headersExporting PatchesExport using the cables command line interfaceExport via IframeExport creating a standalone executableExport to github (pages)Export and deploy to netlifyExport a ZIP fileExternal triggers / functionsUsing variablesPreviewing / uploading exported cables patchesExamples for EmbeddingPermissionsUsersPatchesTeamsOpsMultiplayerPatchlistsCoding OpsCreating AttachmentsGeneral op/Port CallbacksPortsDynamic PortsArray PortsBoolean portsInteger Number PortsObject PortsString portsTrigger PortsFloating Point Number PortsGUI/UI attributesHello Op - Part 1LibrariesDeveloping OpsRenaming / Creating a new versionCreating Viz OpsGuidelinesObject PortsWriting ShadersWeb Audio Op DevelopmentHTML And CSS In CablesLightingLightsShadowsWorking With AudioBasic Audio SetupWorking with EffectsReal-Time Audio Analyzation & Audio VisualizationOffline Audio Visualization & AnalyzationOptimizing Performance In PatchesTools for debugging your patchHow to optimize cables patches with the Performance opHow to optimize cables patches with the ProfilerCommon pitfalls with the "usual suspects"Optimizing arraysDebugging Shaders with ShaderInfoFAQAudio in web browsersHow to make demoscene demos with cables.glEmbeddingHow to integrate my cables patch into my CMS (webflow/wix/squarespace/...)?How to remove grey rectangles on touch (mobile)?Why doesn't the DownloadTexture op work on iOS?How to disable page scrolling on mobile?Mobile tippsHow to run exported patches on your local machineTransparent CanvasFeatures and SupportHow to contribute code to cablesWill there be support for (animated) GIFs?Can i use a website as a texture?Screenshots and Video recordingHow to report a bug in cablesHow can I support cables?Video playback in cablesGeneral questionsWhat is dev.cables.glJavascript Frameworkscordova / phonegapelectronreactvuejsLicenses and paymentWhat license do i need to use cables?Will I have to pay for it in the future?How is my work licensed when using cables?Does cables support midi and OSC?Patch PermissionsMy User Profile & Social MediaShadertoyCables at schools and universitiesTechnical questionsWebGL1 and WebGL2

Patch Permissions

A cables patch can have different states and also different people working on the project. Here is a rundown of the
different levels of permission cables offers to teams and individuals.


You can, and should, make a patch public to show it to the world and the cables community. Every person with the
URL to your patch can look at it on the patch page, open the editor to see how you patched it all together and
clone it to remix the patch. If you come across a public patch and want to remix it, we strongly encourage you
to adhere to the licence the patch has been published with. Credit the author(s)!

While it is possible to view a patch with user-ops on the patch page and the editor, cloning such a patch will
need the patch owner to be a collaborator (see below) in the patch for their user-ops to work.

If you want to be a bit more restrictive on who to send your patch to, you can create a secret link. From the
patch settings, create a secret link and send it to the person you want to have a look at the patch (convenient for
sending previews to clients, for example).

Any person with a secret link can view the patch on the patch page, but not open it in the editor. Access to
the patch can be requested though, it is then up to you to decide the level of access you want to grant (see below).

Team Patch

If you work in a larger group of people, or have a project that spans multiple patches, you can easily group them
together by creating a team. Any patch associated with the team will allow the team members to see it on the patch
page and in the editor.

Team members will also be able to request access (in that case "Full Access" (see below)) to a patch. It is up
to the owner of the patch to grant access to patches. You, as the owner, will find new request for access on the
activity feed after clicking on the red bubble notification on your welcome page.


When inviting people to your patch, or on replying to any request for access to a patch, the owner can decide on
the level of access to grant to a user.

"Read Only" means that the person will be added as a collaborator to the patch, can view the patch on the patch
page and open the editor. They will also be able to clone your project and remix it.

Full Access

People with full access to a patch will be able to both view the patch and edit it. They are also able to decide on
the permission levels of other collaborators and invite new ones, as well as edit patch settings.


On top of all the other permissions that full access grants to collaborators, the owner can make other people owner
of the patch. The owner is the person to be shown in all the overviews for patches on and can configure some options
for exports that need third-party credentials (i.e. github-pages or netlify).

Also the owner of a patch will be in charge to manage all requests for access.

help cables get better and edit this file on github