Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Fluid Dialogue review

Free#63 of 65 in Template Engine Software

A capable Unity dialogue editor, but not a general-purpose template engine.

0.7/10Editor score
Fluid Dialogue0.7 Visit Fluid Dialogue

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Fluid Dialogue is an open-source dialogue system for Unity projects. It targets solo developers and small teams that need to design interactive conversations, hubs, and choices in a visual editor rather than authoring dialogue as a general-purpose template. Dialogue data uses Unity ScriptableObjects, while an event-driven playback controller handles runtime presentation. A spell-check utility for dialogue nodes is included for content review.

Its standout capability is branching dialogue design. The editor supports drag-and-drop graphs with dialogue, hub, and choice hub node types, and conditions can reference local or persistent global variables. Custom actions and conditions extend conversation logic, while custom nodes and UI integration APIs provide ways to connect the system to a project’s interface and gameplay code. Installation runs through Unity Package Manager, and example workflows are included. Unity is the stated integration, making the package a focused fit for that engine’s ecosystem.

Fluid Dialogue’s scope is also its main boundary in a template-engine category. The published feature set centers on dialogue authoring and playback, not general-purpose template rendering, so teams seeking a broader rendering engine should choose another product. It is also tied to Unity rather than offering a cross-engine workflow. Community support and documentation are the stated support channels, which suits independent or small teams that can work within that model. Choose Fluid Dialogue when branching conversations, variable-driven conditions, and extensible Unity integration are the priority; choose an alternative when templates must render beyond dialogue or outside Unity.

Fluid Dialogue pros and cons

  • Where it wins
    • Visual graph editor with dialogue, hub, and choice hub nodes
    • Branching logic uses local and persistent global variables
    • Custom actions, conditions, nodes, and UI integration APIs
  • Where it doesn't
    • Designed for Unity, so it does not serve cross-engine projects
    • Dialogue graph focus is not a general-purpose template renderer
    • Support is centered on community channels and documentation

Fluid Dialogue fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update