Magnific Save To (project/folder)

Magnific's nodes in ComfyUI don't run anything locally. Every generation, retouch and background removal is a job submitted to Magnific's servers and handed back into your graph. That's not a hidden caveat - it's the entire design, and this pack's own source comments put it plainly: these nodes do nothing useful offline, "the nature of the service, not a fault in the port."

Which is why the least interesting-looking node in the family is the one to add first. Magnific Save To picks a project and a folder inside it, and that choice is a MAGNIFIC_FOLDER output you feed into every other Magnific node. Skip it and your results land in your Personal project instead, which works fine until you have fifty of them and no idea which run made what.

It's also where you sign in. If you're not authenticated, the node shows a Sign in to Magnific button, and there's a matching message at ComfyUI startup. Click it, your browser opens, you approve there, and you come back with the node populated. Your password never touches ComfyUI.

What you set

Two widgets, both enums: project and folder. Both are filled from your account, and both are empty until you're signed in - an unpopulated list reads - sign in (Magnific menu) and press R to refresh -, which is less cryptic than most cloud nodes manage. The folder list narrows to whatever project you picked; (project root) is a valid choice and the default.

R refreshes the lists, and there's a Magnific menu in ComfyUI's interface that does the same. If you create a project in the browser and it isn't in the dropdown, refresh before you start debugging.

The single output is folder. Everything that produces or edits media takes it: the image, video and music generators, the upscaler, retouch, skin enhancer, background removal, voiceover, stock picker and creation picker.

Install

The Magnific nodes ship inside this pack - they were ported in from the vendor's own magnific-comfyui (0.7.0), so installing the pack gets them:

cd ComfyUI/custom_nodes
git clone https://github.com/Code2Collapse/ComfyUI-CustomNodePacks.git

Or "CustomNodePacks" in ComfyUI Manager, then restart ComfyUI. Magnific's own distribution route - a zip from https://www.magnific.com/plugins - is what the upstream nodes document, and it's the same integration; the upside of using it is that upstream updates land first, the downside is two copies fighting over the same node names. Pick one. If you'd rather install the vendor's pack separately, delete the Magnific nodes from this one's registration or don't use both at once.

Sign-in state lives at ~/.magnific/comfyui_auth.json - the vendor's own path, deliberately, so a machine signed in through either pack stays signed in. To sign out, delete that file.

The honest framing

These are metered API calls against a subscription you pay for. Nothing here is CPU or VRAM work; the cost is money and time per call, and your prompts and reference images leave the machine. Our own KB writes about this category with some weariness - the community's default position is that API nodes are for models you genuinely cannot run locally, and resents them as a default. Magnific is an interesting case in that space, because the upscaler has a long history of open-source competitors while the generation side is a storefront for other people's models.

Practical read: use these when Magnific is what you're already paying for and you want it inside the graph, next to your local masking. Don't wire a whole pipeline around them and then discover the credit meter.