NibWP connects to Figma, pulls your frames into a local library, and lets an AI agent turn them into native WordPress pages with whichever builder your site already runs. It reads the real design, not a screenshot, and never modifies anything in Figma.
How it works
Pulling and converting are two separate steps on purpose. You pull a design once; you can convert it many times, into different builders, whenever you need it.
- 1Connect a Figma account. A read-only token takes about two minutes.
- 2Pull a frame, a whole file, or an entire team into your library.
- 3Each frame is cached as a 2x image plus its real design tokens: colors and type ramp.
- 4Ask the AI agent to build it. NibWP picks the builder your site runs and saves a draft.
What gets extracted
Every pulled frame carries more than a picture.
- 1A 2x render, stored in your media library.
- 2The color palette, ranked by how much of the design uses each color.
- 3A type ramp (display, headings, body, small) collapsed from the text styles in the frame.
- 4The structure: sections, containers, text nodes and component instances.
Supported builders
Conversion is builder-agnostic. NibWP detects what your site actually runs and hands the design to that builder own validated pipeline: Etch, Bricks, Elementor, Kadence and Oxygen. If no builder skill is present it falls back to core WordPress blocks, which work everywhere.
Read-only: NibWP can read the files your Figma account can open, and can never change your designs.