Skip to main content
Question

Does documentAccess: 'dynamicPage' cause performance drop ?

  • May 14, 2026
  • 1 reply
  • 7 views

Mridul_Kumar

I have a plugin to find accessibility issues. We fetch images, traverse the tree and do all sorts of operations but ever since migrating to the new documentAccess: ‘dynamic-page’, the plugin has become slower.

1 reply

Celyn_L
Figmate
  • Figmate
  • May 15, 2026

Hi ​@Mridul_Kumar — Celyn from Figma Community Support here.

Thanks for reaching out and for sharing these details, happy to help! 

To answer your question, as your plugin traverses the document tree and performs accessibility checks across the file, documentAccess: 'dynamic-page' can affect performance depending on how the plugin accesses the document.

With dynamic page loading, pages are loaded as they’re accessed. Plugins that traverse large parts of a file or use methods like findAll() across the document may take longer while additional pages are loaded.

One thing you could try is calling:

await figma.loadAllPagesAsync()

before running your traversal or findAll() operations. In some cases, this may help by loading all pages before the scan begins, although performance may still vary depending on the complexity and size of the file.

I’ve also gone ahead and created a support ticket for you so the team can take a closer look into this behavior. Your ticket number is #1904241.

It will be really helpful if you could reply directly to the ticket with:

  • A screen recording of the slowdown occurring, if possible
  • Whether this happens in both the browser and desktop app
  • The plugin URL you’re testing with

You may also find this developer resource helpful for reference:
BYFP: Building Your Plugin

Hope this helps, and please keep an eye on your inbox - someone from the team will be in touch to work with you on this soon.