The part of your work nobody gets to see
I spend way more time in ComfyUI's node editor than I do writing prompts. Picking the right checkpoint, wiring up ControlNet, figuring out which sampler actually works for a given style — that's where the real decisions happen. But when I post the final image somewhere? All that work just... vanishes.
Someone comments "this is sick, how'd you make it?" and suddenly I'm screenshotting my node graph, typing out settings in Discord, uploading a .json to Google Drive. It's annoying. And the person on the other end gets a blurry screenshot and a file with zero context.
I kept thinking: why isn't the workflow just *part* of the portfolio?
How we all share workflows right now (and why it's a mess)
Let's be honest about what the current options look like:
**Screenshots.** You take a screenshot of your ComfyUI canvas and post it. Someone squints at it, can't read the node values, asks you to zoom in. You take another screenshot. Repeat.
**JSON files on Google Drive.** It works, technically. But the file sits in a folder with no connection to the image it made. Six months later, even you don't remember which workflow went with which piece.
**Reddit/Discord threads.** You paste the workflow in a reply. The thread gets buried. Gone forever unless someone bookmarked it.
**CivitAI.** They have some workflow stuff, but it's really a model hosting site. Your workflow ends up in a sea of LoRA downloads. Not exactly a portfolio.
I'm not saying these are terrible — I've used all of them. But none of them feel like the right answer. The workflow should live *with* the artwork, not scattered across five different platforms.
What we built on PixelAI
We added ComfyUI workflow support directly into the upload flow. Here's what that actually means in practice.
Drop in your .json
When you're uploading a piece, there's a spot to attach your workflow file. Works with both File → Save and File → Export (API Format) from ComfyUI. Drag, drop, done.
It reads your nodes automatically
This is the part that saves the most time. The system parses your workflow and pulls out the checkpoint, sampler, scheduler, seed, steps, CFG — all of it. No more manually typing "DPM++ 2M Karras, 30 steps, CFG 7.5." It just reads the KSampler node and fills everything in.
LoRAs, ControlNets, IP-Adapters — those get picked up too. If the node's in your graph, it shows up in the metadata.
The interactive graph thing
Okay, this one's genuinely cool. Your workflow renders as an actual interactive graph. You can zoom in, pan around, click on nodes. Everything's color-coded:
- Purple → loaders (checkpoints, LoRAs)
- Blue → samplers
- Yellow → conditioning (CLIP encode, ControlNet)
- Cyan → latent stuff
- Green → image operations
- Red → outputs
- Pink → custom nodes (they get a little ⚡ badge)
The connections between nodes show data types (IMAGE, LATENT, MODEL) and they're animated so you can trace the flow. There's a minimap for big workflows and a fullscreen mode when you really want to dig in.
Is it as good as actually opening the workflow in ComfyUI? No, obviously. But for browsing someone's portfolio and understanding how they built something? It's way better than a screenshot.
Download with one click
Viewer sees your workflow, clicks download, gets the .json. They open ComfyUI, load it, and they have your exact setup. That's it. No "hey can you share the workflow?" in the comments. No broken Google Drive links three months later.
You decide who sees it
The workflow sits behind the same gate as your prompt. So if you've got your prompt set to public, the workflow's public too. If you keep your prompt private, viewers use one of their 5 free daily reveals (or they're a Pro subscriber) to unlock the prompt, generation details, *and* workflow all at once.
This actually makes workflows interesting as premium content. The image is free to view, but the "how I made it" bundle — that's gated.
Tips from actually using this
**Use File → Save, not Export API.** Both work, but Save keeps the node positions and titles. The graph looks way better.
**Clean up your canvas first.** We filter out MarkdownNote nodes automatically, but if you've got a bunch of disconnected test nodes floating around, the graph gets messy. Take 30 seconds to delete the junk before exporting.
**Don't just title it "SDXL ControlNet."** That tells me nothing. "Turning street photos into Ghibli scenes with depth-guided SDXL" — now I want to click on it. The workflow handles the technical side; your title and description handle the *why*.
**If you teach, this is huge.** Instead of writing a step-by-step tutorial that's outdated in two weeks when some node gets updated, just share the working workflow. People can download it and poke around. Way more useful than screenshots with red arrows.
Why this matters beyond just convenience
I've noticed a few things since we launched this:
People actually look at workflows when they're easy to access. It sounds obvious, but when it's a Google Drive link in a Discord DM, nobody bothers. When it's right there on the portfolio page with a nice graph? People click.
It also changes how the portfolio reads. A post with an image, a prompt, and a workflow tells a different story than just an image. It says "I know what I'm doing, and I'm willing to show you exactly how." That matters if you're trying to get freelance work or build an audience.
And selfishly — seeing which workflows get downloaded the most tells you what people actually care about. Turns out my ControlNet stuff gets way more downloads than my vanilla txt2img workflows. Good to know.
Try it out
If you've got a PixelAI account, just go to the upload page and look for the workflow upload in Advanced Parameters. If you're new, signup takes like 30 seconds.
Got a backlog of pieces without workflows? You can edit existing posts and add them later. Start with your most interesting pipelines — the ones where the workflow is actually doing something clever, not just checkpoint → sampler → save.
The image is what people see. The workflow is how you got there. Both deserve to be in your portfolio.