GravityView displays Gravity Forms entries, not custom post types or custom fields. Its data source is your form submissions, so if you collect data through Gravity Forms, GravityView shows it on the front end with no content modeling. It can edit posts created by the Gravity Forms + Custom Post Types add-on, but it is not a general custom-post-type display tool. If your site is built on custom post types and custom fields, that is Toolset’s (OnTheGoSystems) territory. You can see what GravityView displays on the GravityView product page.

Not natively. Toolset works with native WordPress data such as custom post types, custom fields, taxonomies, and users, and it has no built-in Gravity Forms entries integration. To show Gravity Forms data in Toolset, you would write each submission into a custom post type using a connector or custom code, then display that post type. If displaying Gravity Forms entries is the main job, GravityView reads them directly and skips that step.

This is one of Toolset’s clear strengths. Toolset offers native post relationships, from one-to-one to many-to-many, between any content types. GravityView does not model content-type relationships in the same way, but it can join and display data across multiple forms with its Multiple Forms feature, available in the higher tiers, which covers many one-to-many cases such as showing a parent record alongside its related entries. For a deeply relational data model with many connected content types, Toolset is the more natural fit; for joining related form data, GravityView handles the common cases.

Both build directories, and the better fit depends on where the data comes from. If people submit listings through a Gravity Forms form and you want a searchable directory with front-end editing and approval, GravityView is the more direct path. If your listings are custom post types with relationships, custom fields, and full template and archive pages, as on many real estate and classifieds sites, Toolset is built for that kind of structured site. Our Gravity Forms directory guide shows what the GravityView approach looks like.

Yes, though at a slower pace than before. OnTheGoSystems paused new-feature development for Toolset in 2022 to wait for WordPress full site editing to settle, while continuing to ship bug-fix, security, and compatibility updates. It later resumed feature work under new leadership and added full site editing support in 2026. So Toolset is actively maintained rather than abandoned, but its release pace is slower than GravityView’s, which shipped a major 3.0 version in 2026. If long-term development speed matters to you, that difference is worth weighing.

Neither tool requires a page builder. GravityView builds views in its own drag-and-drop editor and embeds them with a shortcode or block, and Toolset builds everything in the WordPress block editor. The practical difference is scope. GravityView is a focused display layer for form data, so there is less to learn. Toolset is a full site-building suite covering content types, forms, search, templates, and access control, which is more capable but has a steeper learning curve. Choose based on whether you need a focused tool or a complete framework.

GravityView requires a separate Gravity Forms license (from $59/year), and GravityView core costs $119/year for a single site, with lifetime licenses available from $499. Toolset is priced in euros and bundles its whole suite into one license: €69 for the first year for one site (renewing at €51), up to €299 for unlimited sites, with no lifetime option since Toolset discontinued it. Both offer a 30-day money-back guarantee. For a brand-new site, Toolset’s single bundle can cost less than GravityView plus Gravity Forms; if you already run Gravity Forms, GravityView adds one focused layer. Current figures are on the GravityKit pricing page.

Both can, with WPML doing the translation. Toolset has an advantage here because it comes from OnTheGoSystems, the company behind WPML, so the two integrate tightly for translating content types, fields, and templates. GravityView also works with WPML to translate View labels and search inputs, though the entry data itself is not translated automatically. If multilingual content is central to the project, Toolset’s WPML pairing is the stronger option. Our multilingual directory guide covers the GravityView and WPML setup.