Integrations

You can paste or drag and drop bitmap images and SVGs into nifdi.

For safety, SVG imports are sanitized. Scripts, animation, and external file references are stripped out.

If an imported image is exactly square, nifdi treats it as an icon. Otherwise, nifdi creates a container and sets the image as its background.

The simplest way to export is to select objects in nifdi and copy to clipboard. This will put both bitmap and SVG versions of the selection on your clipboard.

You can also copy or download these images as PNG of SVG files from the Download panel on the right side of the editor.

You can paste directly into any application you choose. For example, you can paste directly into a slide deck, or an email.

Also note that SVG is effectively plain-text on the clipboard, so you can also paste it into a text editor or IDE.

.nifdi.svg exports are fully valid SVG files, and they also contain the additional markup nifdi needs to reopen and edit the diagram structure.

This makes sharing straightforward: recipients can view the file anywhere SVG is accepted, yet still edit, adapt, or repurpose it in nifdi as needed. No separate 'source file' is required.

Files are self-contained. Required fonts and imported graphics are embedded. Third-party icons include their attribution and license metadata in the file.

nifdi does not currently provide cloud storage. If you want sync or sharing, store your files in your preferred cloud file service.

In Chrome (but not yet in many other web browsers), you can open files directly from local disk and keep editing them in place.

Changes are auto-saved, so you do not need to keep re-exporting after each edit.

Save .nifdi.svg files in a GitHub repository and they render anywhere images are supported, such as checked-in files, README files, wiki pages, and pull request comments.

You can also open files from a checked-out Git repository using the Files on Disk flow.

nifdi ships an MCP server so agents like Claude Code, Claude Desktop, and Cursor can create and edit diagrams as files in your repository. Diagrams live as .nifdi.svg files — committable, diffable, and branchable like source code. No account and no cloud: the server runs on your machine and the diagram never leaves it.

For Claude Code, run:

claude mcp add nifdi -- npx -y @nifdi/mcp@latest

For Claude Desktop, Cursor, and other MCP clients, add this to your MCP configuration (claude_desktop_config.json, .cursor/mcp.json, or equivalent):

{
  "mcpServers": {
    "nifdi": { "command": "npx", "args": ["-y", "@nifdi/mcp@latest"] }
  }
}

The agent's workspace is the directory the server is launched in (usually your project). Optional environment variables: NIFDI_ROOT to point the workspace at a different directory, NIFDI_PORT for the live-preview server (default 4310, off to disable), and NIFDI_OPEN_BROWSER=false to stop the preview opening on the first edit.

The same command is a small CLI for git workflows: npx -y @nifdi/mcp render refreshes the rendered image after hand-editing the embedded XML (--check is a CI lint), and git can be configured to diff and merge diagrams on their canonical XML only — see the package README.