Configuration reference¶

Environment variables, ports, and paths used by the three Kanzi Figma Importer components.

Environment variables¶

Most users do not need to set these. The Kanzi Studio plugin auto-discovers the bridge server in standard install locations, and the standalone installer sets FIGMA_BRIDGE_PATH automatically for environments where auto-discovery cannot find it. The table below is for reference and for advanced users who want to override the defaults. No changes to these variables are needed for a normal install.

Variable	Used by	Default	Purpose
`FIGMA_BRIDGE_PATH`	Kanzi Studio plugin	auto-discovered (also set by the standalone installer)	Absolute path to the `feasibility-bridge` folder. Optional — the Kanzi Studio plugin normally finds the bridge automatically (it looks for `feasibility-bridge` next to its own DLL, then under the Kanzi plugins folder, then beside the open project). Set this only to point at a bridge in a non-standard location.
`KANZI_DIR`	`tools/build-all.ps1`, `tools/install.bat`	newest by name	Override the Kanzi Studio version directory the build / install scripts target.
`KANZI_UI`	`tools/build-all.ps1`	(unset)	Override path to a source-built Kanzi Studio (for the dev build path).
`PORT`	`feasibility-bridge/server.js`	`3847`	Override the bridge server’s WebSocket port.

Ports¶

Port	Component	Purpose
3847	bridge server	WebSocket (Control Channel) + HTTP (Data Channel)

The bridge server listens on 127.0.0.1:3847 (localhost only). To override the port, set the PORT environment variable before starting the bridge server.

File system layout¶

Per-project (Kanzi Studio side)¶

Path	Contents
`<project>/Fonts/`	TTF and OTF font files. Place commercial fonts here for the local-folder fallback.
`<project>/Images/Figma Images/`	Imported PNG / JPG textures from Layout transfers.
`<project>/FigmaImages/Gradient Images/` and `<project>/FigmaImages/SDF Images/`	Gradient strips and SDF shape textures, at the project root.
`<project>/Shaders/`	Generated shader files for the shape material pipeline.

Per-Kanzi Studio-install¶

The exact layout depends on the install path you used (see Kanzi Figma Importer 2.0).

Path	Contents
`%ProgramData%\Rightware\Kanzi <version>\plugins\FigmaImporter\` (KPM install)	The full Kanzi Figma Importer bundle that the Kanzi Package Manager deploys: the Kanzi Studio plugin DLLs (`FigmaImporter.dll`, `FigmaImporter.Core.dll`, `Newtonsoft.Json.dll`), `figma-importer.manifest.json`, the `feasibility-bridge\` folder (the bridge server, plus `cloudflared.exe` for online mode), and the `FigmaPlugin\` folder (the Figma plugin, including `manifest.json`).
`%ProgramData%\Rightware\Kanzi <version>\plugins\` (standalone installer)	The plugin DLLs only (`FigmaImporter.dll`, `FigmaImporter.Core.dll`, `Newtonsoft.Json.dll`). The standalone installer can deploy these to every selected Kanzi version simultaneously.
`%ProgramFiles%\Rightware\Figma Bridge\` (standalone installer only)	Bridge server (`FigmaBridge\`), Figma plugin files (`FigmaPlugin\`), offline documentation (`docs\`), and the uninstaller (`unins000.exe`).
`%LOCALAPPDATA%\Rightware\…`	Kanzi Studio user state (not modified by Kanzi Figma Importer)

Logs¶

Component	Where logs go
bridge server	Standard output (the terminal that started `server.js`).
Kanzi Studio plugin	Debug Log dock + Kanzi Studio output panel
Figma plugin	Browser developer console (Figma Desktop and Figma Online)

Cloudflare Tunnel (online mode)¶

Kanzi Figma Importer ships feasibility-bridge/cloudflared.exe. The Kanzi Studio plugin starts and stops the tunnel automatically when Online connection is enabled in Settings. The tunnel generates an ephemeral *.trycloudflare.com URL and closes when the connection ends.