

Gallery Plugins Supported
Are you tired of other gallery plugins?
Are you looking for a different gallery plugin to try out?
Are you looking for the best gallery plugin with the most free features?
Now you can easily and effortlessly migrate to the best WordPress gallery plugin : FooGallery!
Migrate to FooGallery from other gallery plugins, including:
Features:
For smaller migrations, FooGallery Migrate stores progress and history in WordPress options. Larger migration histories can use substantial memory when stored this way. On single-site installations, you can choose database-table storage so the plugin can read and update smaller portions of migration state instead of repeatedly loading the complete history.
Open FooGallery > Migrate! > Settings, choose Database tables under Migration Storage, and click Change storage. The plugin copies and verifies existing migration data before switching. Your galleries, albums, media and page content are kept. Storage never switches automatically. Returning to WordPress options is available when the current migration data fits the conversion limits; a large history may need to be reset first.
The plugin recommends tables when saved migration data or discovered gallery/image counts indicate a larger migration. Gallery discovery saves a small count summary for this advice and the Troubleshooting tab, without loading every source image just to display the recommendation. Counts describe source gallery/image entries and can include the same image in multiple galleries. Use Refresh Galleries to update saved counts.
Keep Page Size above zero to display galleries in pages. Images Per Turn controls how many images are processed in each gallery migration request. The shared progress dialog shows image progress within the current gallery; Stop waits for the current batch, and saved progress can be resumed. Failed gallery migrations show an error and offer Retry Migration.
Database-table storage is available on single sites. Multisite continues to use WordPress options. Redis is not required.
Development and QA have exercised these separate workloads:
The large-gallery journeys ran with a 256 MB PHP memory limit. Additional testing covered storage switching in both directions where the data fits, interrupted changes and recovery, Stop/resume, missing images and retries, albums, blocks/shortcodes, NextGEN image tags, and compatibility with persistent Redis object caching. Reset, removal and uninstall checks verified that migrated/source content and media were kept.
As of 27 October 2026, the maintained automated suite passes 1,847 tests. The latest reset recovery also passed a native two-connection database test: an expired marker belonging to a connected writer blocks reset; after the writer disconnects, reset clears its marker and history while keeping preferences.
These results come from separate development builds and QA runs. They are tested workloads, not maximum supported sizes or a guarantee for every source plugin and hosting setup. Table storage reduces migration-state memory use; image dimensions, file sizes, metadata and very large individual galleries can still affect memory and request time.
Spin up a demo site with FooGallery Migrate and all supported galleries, so you can see how it works:
Try Migrate Demo
The lite version of Envira includes basic gallery features, like unlimited gallery creation with drag n drop reordering. There are a few settings to tweak within Envira, but to get the most out of it, you will need to upgrade to a paid version.
OR, change to FooGallery! The free version of FooGallery has tons more features, including being able to choose different gallery layouts, like masonry, image viewer, portfolio.
Modula has 4 gallery layouts VS the 7 that come free with FooGallery. Modula also has a ton of settings to customize your galleries, but not as many as FooGallery offers.
NextGen has 3 gallery styles and a batch upload feature. More advanced features are only available with the paid versions of NextGen.
FooGallery free has 7 gallery styles and a load of different settings to customize it to look perfect for your website and theme.
FooGallery Migrate can detect “Album and Image Gallery Plus Lightbox” galleries directly from WordPress database records, so the source plugin does not need to be active or loaded during migration.
FooGallery Migrate detects the exact current-site WP Photo Album Plus database tables even when WP Photo Album Plus is inactive. It creates one FooGallery gallery for each source album containing a supported, public local image and preserves image titles, descriptions/captions, alternative text, valid dates and deterministic source order.
WP Photo Album Plus stores images outside the WordPress Media Library. FooGallery Migrate supports its current flat and tree upload layouts and imports canonical local JPG, JPEG, PNG, GIF and WebP display files. WebP files require image inspection support in the site’s PHP runtime; when unavailable they are skipped safely. Missing or malformed files, invalid rows, trashed/deleted items, capability-restricted albums, non-public or unknown statuses, and video, audio, PDF or other unsupported payloads are skipped rather than creating broken attachments.
Nested WP Photo Album Plus albums cannot be represented exactly because FooGallery albums contain galleries, not other albums. A source album with child albums is therefore offered as a FooGallery album containing its own non-empty gallery and all non-empty descendant galleries in a flattened list. Empty branches are omitted.
Only WP Photo Album Plus shortcodes and blocks containing one explicit positive numeric album value can be replaced automatically. Dynamic or virtual expressions (including names, encrypted IDs, #last, tag/search/query selectors and combined album expressions) are intentionally left unchanged for manual review. Random or unknown WP Photo Album Plus image order is converted to stable source-ID order; supported configured order modes use source IDs as deterministic tie-breakers.