Converting a 15,000px Figma landing page to WordPress, a section at a time
Tall Figma frames used to run Figma out of memory. FigWP now converts frames up to 20,000px in strips and joins them into one Elementor page, billed once.
In this article
The first tall page we converted was a docs landing page, 15,395px from the hero to the footer. Converted whole, it ran Figma out of memory halfway through reading the layers. The page was fine; the method was not. Here is what changed, and what it means for the long landing pages that are most of what people convert.
The frame is cut where nothing crosses
A frame over 5,000px, or with more than 1,500 layers, is no longer read in one go. FigWP asks the plugin for a plan: cut the frame into strips of roughly 3,000px, always along a horizontal line that no layer crosses. Sections stay whole; a card grid never gets split through its middle.
Each strip is then converted on its own, as if the frame had been cropped to it. The plugin only ever holds one strip’s layers at a time, which is what keeps Figma comfortable.
The strips become one conversion
The parts are stacked in order into a single conversion. There is one reservation on your plan, made once at the frame’s full height, and one page charged when the result is imported. The 15,395px page is a page, not five.
Your AI app sees this as a job that takes a few turns. Each request converts what fits in about 40 seconds and returns a job id; the next turn continues from there. If the app’s turn ends in the middle, nothing is lost and nothing is repeated.
The limit, and what to do above it
A single conversion is capped at 20,000px. Above that, FigWP refuses before it reads a single layer and asks you to split the design. Splitting is cheap: cut the design into page-sized frames at a section boundary, convert the first, import it, then convert the next and ask the app to add it to the same draft. The parts are appended in order, and a part sent twice is added once. Each frame is its own page on the plan.
Importing is in steps too
A long page has a lot of images. The import used to copy every image before saving, and a page with a hundred images outlived the app’s patience. Now the draft is created empty, images are copied into the media library ten at a time, and the content is saved last, pointing at the attachments. A timeout costs nothing: the app continues the import from where it stopped.
What to expect
A 15,000px page converts in a few minutes and a handful of turns. The result is one Elementor page with one section per band of the design, each a widget where the mapping found one. Images are in the media library. The page is a draft until you publish it.
The tall pages doc has the limits in one place, and the plans doc explains why a frame’s height never costs you a second page.
Frequently asked questions
Is a tall frame more than one page on my plan?
No. A frame up to 20,000px is one conversion and one page, however many strips it is cut into. Only a design split into several frames costs a page per frame.
Why not just convert the whole frame at once?
Figma reads the frame's layers in memory, and a 15,000px page with thousands of layers exceeded what it could hold. Strips keep the plugin working on one section at a time.