Core Nodes vs Custom Nodes

overview not all nodes are built the same in floyo, you can use both core nodes and custom nodes in any workflow understanding the difference helps you build more effectively types of nodes true 203,203,205 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type core nodes core nodes are the default set that comes with comfyui these are the basics, the essential tools that power almost every workflow what core nodes include true 305,306 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type core nodes are stable, well supported, and usually all you need for common workflows if you've used comfyui before, you'll recognize them right away custom nodes custom nodes come from the broader comfyui community or your own team these extend what you can do far beyond the basics what custom nodes can do true 305,306 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type floyo supports over 2,500 custom nodes , and you can load your own too if someone has built it and shared it, you can use it see list of all available https //www floyo ai/all comfyui nodes/status/production on floyo 💡 tip custom nodes are what make comfyui so powerful they let the community solve problems faster than any single team could using core and custom nodes together you can mix core and custom nodes freely most advanced workflows use a combination of both you don't need to know where every node comes from if it works, it works hover over a node for a tooltip or inspect its inputs and outputs floyo makes it easy to experiment without breaking your flow missing custom nodes if you're loading a workflow with custom nodes not currently installed on floyo a message is sent to floyo's developers the team works to install the missing nodes official turnaround time within 72 hours in practice, it's usually much faster you can also proactively request custom nodes see https //docs floyo ai/requesting custom nodes for details how to tell the difference in most cases, you don't need to distinguish between core and custom nodes however, if you're curious true 305,306 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type tips & best practices start with core nodes learn the basics before diving into custom nodes explore custom packs browse installed custom node packs to discover new capabilities check compatibility custom nodes may have dependencies on specific models or other nodes request what you need if a workflow requires a missing node, floyo will install it for you related documentation https //docs floyo ai/nodes https //docs floyo ai/adding nodes https //docs floyo ai/requesting custom nodes https //docs floyo ai/floyo api nodes