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 overview node type source availability core nodes built into comfyui always available custom nodes community or third party 2,500+ pre installed; more added daily 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 category examples model loaders load checkpoint, load lora, load vae samplers and schedulers ksampler, ksampleradvanced prompt inputs clip text encode, conditioning image outputs save image, preview image conditioners controlnet apply, apply lora upscalers upscale image, upscale latent image processing resize, crop, combine, mask 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 use case examples specialized lora loaders advanced lora stacking, conditional loading custom samplers alternative sampling algorithms text tools logic gates, advanced math, string manipulation animation & ui control nodes for scripting and batch workflows non image tasks audio, data processing, function chaining 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 💡 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 indicator meaning node pack name in browser custom nodes show their pack name (e g , "comfyui impact pack") missing node errors usually indicates a custom node that needs installation 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