Free Download Gravity Forms 3.1.3.3 — Nulled FAQ

What Gravity Forms is useful for

Gravity Forms is a WordPress form builder for collecting structured information through your own site. Its field rules, page breaks, stored entries and CSV exports make it useful for project enquiries, applications and other requests that need more structure than a name-and-message box. The practical question is whether those pieces work together for the workflow you intend to build.

We tested the supplied Gravity Forms 3.1.3.3 package with a two-step project-request form and a separate file-upload form. The first form asks whether a request is personal or business-related, requires a company only for business requests, then collects project details. The second accepts one PDF or PNG with a 1 MB limit. The observations below distinguish native API checks, actual HTTP submissions and the features we did not exercise.

• Official Gravity Forms feature overview

The installation and test boundary

The functional run began at 10:38:28 UTC on 16 October 2026. It used fictional names and an example.invalid email address in a private, isolated installation. The test is a record of this environment, not a cross-theme compatibility survey, load benchmark or promise about another hosting configuration. The WordPress upload ceiling was 256 MiB; the stricter 1 MB field setting was the boundary exercised by the upload test.

What changed in 3.1.3.3

The official changelog identifies a fix for saving text-field values when conditional logic is combined with Hidden visibility. Our Company field uses ordinary conditional display; that is not the same configuration, so these results should not be read as a regression test of that specific fix. The changelog already lists 3.1.3.4 at the time of review. This page deliberately identifies the supplied and tested 3.1.3.3 package rather than calling it the latest release.

• Official Gravity Forms changelog

A company field that becomes required only when it is relevant

The first step contains Contact name, Email, Request type and Company. Company is marked required, but a conditional rule shows it only when Request type equals Business. That combination matters: an irrelevant hidden field should not block a personal enquiry, while a business enquiry should not silently omit the company.

All three cases behaved as intended in the native validation calls. This matches the documented rule model: one field’s value controls whether another field is shown or hidden. The fixture uses simple plain-text values, personal and business, rather than display text containing HTML.

• Official guide: enabling conditional logic for fields

Two steps, with validation at the step that needs it

A page break separates contact information from Project details. With valid first-step values, the API returned page_number 2. Submitting the second step with Project details empty returned an error for field 6. Supplying the details returned a valid result and page_number 0, indicating completion rather than another page.

A separate browser run reproduced the empty-Company rejection, moved to the second step after Company was supplied and confirmed a saved synthetic submission. The screenshots show that browser workflow; the recorded JSON contains the independent API observations.

The page break is useful when the second group of fields has a distinct purpose. It does not remove the need to validate the earlier selections or keep the form short. Our fixture tests a two-page flow; it does not test conditional page skipping, save-and-continue, accessibility across every browser or a form with hundreds of fields.

• Official guide: conditional logic for multi-page forms

Real file requests: an accepted PNG and two rejected uploads

We first checked the field’s own validator, then sent actual multipart POST requests to the rendered upload form. Each request used the hidden fields returned by a fresh page GET. The upload field allowed PDF and PNG, accepted a single file and had a 1 MB limit. These were real request and storage observations, rather than an inference from the settings screen.

The accepted file was read back from storage: its size remained 68 bytes and its SHA-256 matched the submitted bytes. The wrong-extension response explicitly listed pdf and png as permitted types. The oversized response explicitly reported the 1 MB limit. The upload form contained one saved entry after these three requests, so neither rejected submission created an extra entry.

HTTP 200 alone would not have proved acceptance: all three form responses used that status. We distinguished the confirmation from the rendered field-specific validation message, and checked the stored entry separately. PDF was configured as allowed, but this run did not submit an actual PDF. The multipart requests were scripted. A separate real browser run reproduced the wrong-extension and oversized-file errors; its screenshots appear here.

• Official File Upload field settings and validation

The submitted values survived entry storage and CSV export

The completed project request was submitted through GFAPI::submit_form, then read back as an entry. Its Company value was Synthetic Studio, and the Project details text contained both a comma and quotation marks: Planning, launch and a "quoted" brief. The saved entry preserved that text.

We used the plugin’s native entry-export formatter and parsed its CSV output again. The project text round-tripped unchanged, with doubled quotation marks in the CSV representation. This verifies the stored data and formatter path for the selected fields; it is not a test of a large browser export, scheduled exports or spreadsheet-import behavior in every application.

Saved value:
Planning, launch and a "quoted" brief.

CSV field:
"Planning, launch and a ""quoted"" brief."

For an ordinary manual export, the official workflow is Forms → Import/Export → Export Entries: choose a form and fields, optionally narrow the entries, and download the CSV. The native formatter check here complements that documented workflow; it does not claim we exercised every export option.

• Official entry export workflow
• Official GFAPI submission behavior

Installing the main plugin and rebuilding this small workflow

1. Start with a backup and a staging copy of your own WordPress site. Record its WordPress, PHP, theme and existing plugin versions so an observed problem has a reproducible context.
2. Download the main Gravity Forms ZIP using the versioned button at the bottom of this page. In WordPress, use Plugins → Add New Plugin → Upload Plugin, select the main ZIP, install and activate it. Treat the package record as the description of the supplied artifact.
3. Create the contact fields and a Personal/Business dropdown. Mark Company required, then set its conditional rule to show the field only when the dropdown value is business. Test both branches.
4. Insert a page break before the required Project details field. Embed the form in a page and test moving forward with missing and complete values.
5. For the separate upload check, create a required single-file field with pdf,png allowed and a 1 MB maximum. Submit a small allowed file, a disallowed extension and a file above the limit; then inspect the entry list.
6. Check the saved data and export a synthetic entry before collecting real enquiries. Configure and test your own mail delivery and any external integrations separately.

The two forms are deliberately small. They are a starting point for reproduction, not an application template with payment, anti-spam or CRM behavior already proven. No notification delivery was enabled for these synthetic fixtures.

Main plugin versus the All Addons archive

The first download is the main Gravity Forms 3.1.3.3 plugin ZIP. The second is a dated GPLHub All Addons snapshot containing 158 add-on archives, one supporting Perfex CRM companion archive and an inventory. That inventory describes what was in this supplied snapshot on 16 October 2026; it is not a promise to include every official add-on ever released.

Our functional tests used the main plugin, not all 158 add-ons. A successful form submission does not verify every integration, account entitlement or hosted feature in the bundle. Where an add-on connects to an external service, you still need that service’s own account and configuration, and a separate end-to-end test.

Download the synthetic forms and inspect the recorded outcomes

The fixture download is a native Gravity Forms export of the two tested forms, with notifications disabled. Import it into a staging installation through the form import screen, then inspect the field IDs and settings before using it. The results JSON records the actual environment and observations, including the accepted file’s byte count/hash and the rejection messages.

• Download the synthetic two-form fixture JSON
• Read the recorded functional results JSON

To repeat the requests, GET the rendered upload form, preserve its current hidden fields and send multipart data with a fictional Test case label plus the file. Do not reuse captured state values from another installation. Compare the specific error or confirmation, inspect the entry count and verify the stored allowed file. Repeat the CSV check with text containing a comma and quotes.

What these results establish—and what still needs testing

• Verified in this environment: conditional required-field behavior, two-step validation, a completed entry, native CSV formatting, one real PNG upload, extension rejection and size rejection.
• Not exercised: actual PDF upload, multi-file upload limits, cross-browser file-picker compatibility, save-and-continue, payment processing, CRM feeds or account-backed add-on features.
• External HTTP requests and email delivery were disabled, so this run cannot establish delivery reliability or service connectivity.
• One synthetic workflow is not a compatibility guarantee for a production theme, a caching setup, a large form or every add-on combination.
• The supplied package is modified. These functional observations do not establish vendor byte identity, code provenance beyond the recorded source, or a security guarantee.

When a simpler form is enough

If you only need a name, email address and message, a basic contact-form solution may be easier to maintain. Gravity Forms is more relevant when the work involves field dependencies, several steps, stored entries and a repeatable export process. Before selecting it for a service-connected workflow, list the required add-ons and account costs separately; the local tests on this page do not compare competing plugins or establish those integrations.

Gravity Forms Nulled FAQ

“Nulled” usually describes software whose activation or licence checks have been removed or altered; the word alone does not determine whether a particular use is lawful. GPL-covered code can be studied, modified and redistributed subject to its licence conditions, but this does not grant access to a developer’s account, hosted services, updates or support. We discuss the term here to answer a common search question; the download details separately identify the package source and tested version. Any plugin or theme obtained through an unverified third party can contain unwanted changes or malicious code, whether or not it is labelled “nulled”. Before installing it, you can ask ChatGPT or Claude Code to inspect the extracted source for suspicious behaviour without executing it or sharing credentials. Treat that review as an additional check: AI can miss harmful code or flag harmless code, and a clean result is not a security guarantee.

Can I install the All Addons ZIP directly? No. Extract the outer bundle and choose the individual add-on ZIPs you intend to use. The main Gravity Forms plugin has its own separate download button.

Did this test prove that notifications, payments or a CRM integration work? No. The lab blocked external mail and HTTP requests. Each service-connected workflow needs a separate test with its real configuration.

• GNU GPL FAQ
• GNU GPL version 2 licence text
• Claude Code automated security review documentation