Este plugin no se ha probado con las últimas 3 versiones mayores de WordPress. Puede que ya no tenga soporte ni lo mantenga nadie, o puede que tenga problemas de compatibilidad cuando se usa con las versiones más recientes de WordPress.

SyncS3 Lite


SyncS3 gives Gravity Forms users the ability to push any files to any Amazon S3 bucket. When files are submitted through a form, you can send those files to any Amazon account, and any S3 bucket. Simply add your Amazon AWS credentials, chose which fields should push to S3, and save.

You can even send different file-upload fields to different accounts or buckets. SyncS3 gives you flexible control over which accounts/buckets for sending your files by controlling the settings on global, form, and field levels.

If it doesn’t make sense for you to also store the files locally, you can set the files to be removed from your server after they’re uploaded to S3. This helps reduce the overall disk space of your website.

SyncS3 also includes a WP CLI command for processing all entries, so you can effortlessly send all of your files from all of your form entries to your S3 buckets.

Want to know more about SyncS3? Read about SyncS3’s features.


  • SyncS3 is an add-on for Gravity Forms. Enter your Amazon AWS credentials to connect your S3 account, and select a bucket to host files that are uploaded through your forms. In SyncS3 Pro, you can set different accounts and buckets per form, or per field!
  • SyncS3 file-upload field settings to enable a field to upload files to Amazon S3. Fields do not upload to S3 by default, so you can pick and chose which fields do.
  • In the entry's details, you have links to the files that are now hosted on Amazon S3.


This section describes how to install the plugin and get it working.


  1. Search for SyncS3 in the Add New Plugin section of the WordPress admin
  2. Install & Activate


  1. Download the zip file and upload syncs3-lite to the /wp-content/plugins/ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress

Preguntas frecuentes

How do I use this plugin?

First, install and activate the plugin.

Next, configure your global Amazon AWS settings. These are found in your wp-admin, under Forms –> Settings. This is where you’ll enter your AWS Access Key, Secret Key, Region, and Bucket name.

If you more control over which accounts files are sent to, SyncS3 Pro allows you to send different file upload fields to different accounts or buckets.

Finally, open the Gravity Forms editor for the file-upload field you want to push to S3. In the Advanced tab, enable the Uploads to S3 field setting, and update your form. SyncS3 will now push files submitted via that field to your Amazon S3 bucket when a user submits the form.

Do you offer support for this plugin?

If you have any questions or need any help, please get in touch with us on our website.


No hay reseñas para este plugin.

Colaboradores y desarrolladores

«SyncS3 Lite» es un software de código abierto. Las siguientes personas han colaborado con este plugin.


Traduce «SyncS3 Lite» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios


  • Fixed inconsistency with how S3 URLs were saved.


  • Added entry-specific folder to S3 path to help avoid filename conflicts


  • Adjusted how S3 URLs are saved as entry meta
  • Fixed issue with multi-file uploads
  • Added presigned URLs in the entry’s admin and {s3urls} merge tag
  • Refactored how AWS keys, bucket, and region are retrieved. This makes each variable individually determined, which allows for overwriting a single value (e.g. overwriting just the bucket name for a single field).
  • Switched SyncS3Addon->process_entry() from gform_after_submission to gform_entry_created. The former occurs too late in the process, which wouldn’t allow for using the S3 URLs in the {s3urls} merge tag.
  • Cleaned up field settings display


  • Switched SyncS3Addon->process_entry() from gform_after_submission to gform_entry_created. The former occurs too late in the process, which wouldn’t allow for using the S3 URLs in the {s3urls} merge tag.
  • Style tweaks


  • Fixed issue causing uploads to not send


  • Initial version