Splicing Juncture

Blueprint Graph Exporter

Export Blueprints to readable text and to a documented JSON format.

Blueprints are binary assets. You can't grep them, diff them in a pull request, paste them into a document or an AI chat, or feed them to a script. Blueprint Graph Exporter writes every Blueprint, Blueprint struct and Blueprint enum you pick as:

The output is deterministic: export twice and you get the same bytes, so the files diff cleanly in source control.

Supported: Unreal Engine 5.6, 5.7 and 5.8 on Windows. Editor-only (nothing is added to your packaged game).

Install

  1. Install from Fab (Fab Library > Install to Engine), or copy the BlueprintGraphExporter folder into your project's Plugins folder.
  2. Enable Edit > Plugins > Editor > Blueprint Graph Exporter and restart the editor.

Quick start (editor)

Right-click Blueprints, Blueprint structs or enums in the Content Browser and choose Export to text and JSON. You can also right-click a folder and choose Export Blueprints to text and JSON for everything inside, subfolders included.

The files go to Saved/BlueprintGraphExport/, mirroring the content path (/Game/Characters/BP_Hero becomes Saved/BlueprintGraphExport/Game/Characters/BP_Hero.txt and .bpgraph.json). The folder opens when it's done. Index.md lists everything exported.

Command line

UnrealEditor-Cmd.exe MyGame.uproject -run=BlueprintGraphExport -Paths=/Game/Characters+/Game/Data/S_Item -Out=D:/Exports
Option Meaning
-Paths=A+B Folders (searched recursively) or asset paths, joined with +. Required.
-Out=<folder> Where to write. Default Saved/BlueprintGraphExport in the project. Existing files are overwritten.
-NoText Only JSON.
-NoJson Only text.

The exit code is 0 when everything was exported and 1 when there were problems (listed in Index.md and index.json), so it fits in CI. Example: export on every commit, then commit the exports or attach them to the review.

What's exported

Asset Contents
Blueprint (actors, objects, components, widgets, function and macro libraries, interfaces, level Blueprints saved as assets, ...) Parent class, interfaces, variables (type, default, flags, category, tooltip, RepNotify), components added in the Blueprint (tree, changed properties), inherited component overrides, class defaults that differ from the parent, timelines, every graph (event graphs, functions with their signatures and local variables, macros, the construction script, collapsed graphs) with every node, pin, value and link
Blueprint struct Members with display name, stored name, type, default, tooltip, SaveGame flag
Blueprint enum Values with stored name, display name and number

Text listing

BLUEPRINT /Game/Export/BP_ExportSample.BP_ExportSample
Type: BPTYPE_Normal (/Script/Engine.Blueprint), parent /Script/Engine.Actor, status upToDate

--- VARIABLES ---
  Health : Float (double-precision) [Default] instanceEditable = 100.000000

=== eventGraph: EventGraph (6 nodes) ===
  // COMMENT: Greets the player

  N1 Event BeginPlay [event ReceiveBeginPlay]
    out OutputDelegate : Delegate
    then -> N2.execute

  N2 Print String [call /Script/Engine.KismetSystemLibrary:PrintString]
    then -> N3.execute
    in  InString : String = Hello export
    in  bPrintToScreen : Boolean = true
    ...

=== function: AddHealth (5 nodes) ===
  signature: (Amount: Float (double-precision)) -> (NewHealth: Float (double-precision)), public

  N3 float + float [call /Script/Engine.KismetMathLibrary:Add_DoubleDouble]
    in  A : Float (double-precision) <- N4.Health
    in  B : Float (double-precision) <- N0.Amount
    out ReturnValue : Float (double-precision)

Each node shows its id, title and kind. Inputs show where they come from (<- N4.ReturnValue) or their typed-in value. Execution outputs show where they go (-> N3.execute). Pure nodes are listed just before the node that uses them.

Limits

FAQ

Can I import the text or JSON back into Unreal? No. It's an export for reading, diffing and tools. (To copy nodes between Blueprints, use the editor's copy/paste.)

Is the JSON stable enough to build tools on? Yes, that's its purpose. format.md documents every key. Incompatible changes bump formatVersion; new optional keys can be added without a bump, so ignore keys you don't know.

Does it change my assets? No. It only loads them and writes files to the output folder.

Why are node ids N0, N1, ... instead of names? They follow the layout (top to bottom, left to right) so listings read naturally. Each node also has its guid, which never changes.

Support

splicingjuncture@proton.me

Version history