Contact Form 7


O Contact Form 7 pode gerenciar vários formulários de contato, além de permitir a personalização dos formulários e do conteúdo de e-mails, de modo flexível e uso de markup simples. O formulário suporta envio por tecnologia Ajax, CAPTCHA, filtragem de spam via Akismet e muito mais.

Documentação e Suporte

Você pode encontrar documentos, perguntas frequentes e mais informações detalhadas sobre o Contact Form 7 em Se não conseguir encontrar a resposta para sua dúvida nas perguntas frequentes (FAQ) ou em qualquer documentação, confira o fórum de suporte em Se não conseguir localizar tópicos relacionados ao seu problema específico, publique um novo tópico.

Contact Form 7 precisa do seu apoio

É difícil continuar o desenvolvimento e o suporte para este plugin gratuito sem as contribuições de usuários como você. Se gosta de usar o Contact Form 7 e o considera útil, ajude-nos fazendo uma doação. Isso incentivará e apoiará o desenvolvimento contínuo do plugin e o suporte aos usuários.

Privacy Notices

With the default configuration, this plugin, in itself, does not:

  • track users by stealth;
  • write any user personal data to the database;
  • send any data to external servers;
  • use cookies.

If you activate certain features in this plugin, the contact form submitter’s personal data, including their IP address, may be sent to the service provider. Thus, confirming the provider’s privacy policy is recommended. These features include:

Plugins recomendados

Os seguintes plugins são recomendados para usuários do Contact Form 7:

  • Flamingo por Takayuki Miyoshi – Com Flamingo, você pode salvar as mensagens enviadas através de formulários de contato no banco de dados.
  • Bogo de Takayuki Miyoshi – Bogo é um plugin multilíngue simples que não causa dores de cabeça.


Você pode traduzir Contact Form 7 no

Imagens de tela

  • screenshot-1.png


  1. Faça o upload da pasta inteira do contact-form-7 para o diretório /wp-content/plugins/.
  2. Ative o plugin no menu ‘Plugins’ do seu WordPress.

Você encontrará o menu de ‘Contato’ no seu painel de administração do WordPress.

Para uso básico, dê uma olhada no site do plugin.


Você tem dúvidas ou problemas com o Contact Form 7? Use esses canais de suporte de forma adequada.

  1. Documentação
  2. Perguntas frequentes
  3. Fórum de suporte



ReCaptch v3 is broken and no support for v2

This was our go-to plugin for years. Now it’s been compromised severely in 5.1. Recaptcha v3 simply does not work and it adds a graphic to the front of the website. It’s absolutely terrible. I will be looking for another contact form plugin.

Rollback to Version 5.0.5

Was surprised at how poorly the upgrade did… just rolled back to Version 5.0.5 and the checkbox / I’m not a robot is back.

Can’t quite understand why the upgrade was done?

I’m leaving the 5 star rating for 5.0.5. With the upgrade, I was flooded with junk.

Good plugin (read if you get spam after update)

After serving me well for years, today I updated the plugin to version 5.1, which requires version 3 of reCAPTCHA, yet silently fails (you just start getting tons of spam) if you don’t have the new v3 API keys.

My problem was that I had forgotten I was even using reCAPTCHA, so I ignored the generic verbiage (yes, there are instructions and a FAQ), and I was just surprised and a bit suspicious after getting tons of spam after the update. Because of the spam wave I thought the plugin had been hacked.

Alas, the plugin does not show you any warnings about you still having the old reCAPTCHA v2 setup enabled, it just silently fails and you start getting tons of spam. I think the author could address this, because as the sudden flow of one-star ratings show, this is not clear. The “instructions” are there, sure, but they are generic. As part of the plugin upgrade, I think there should be a specific warning, reminding you that you were actually using reCAPTCHA, and that it’s time to go to and get new v3 API keys. And it should show this warning whenever you open your admin controls, to remind you that you are still using legacy settings.

Leia todas as 1.456 avaliações

Contribuidores e desenvolvedores

“Contact Form 7” é um software com código aberto. As seguintes pessoas contribuíram para este plugin.


“Contact Form 7” foi traduzido para 52 localidades. Obrigado aos tradutores por suas contribuições.

Traduzir “Contact Form 7” para o seu idioma.

Interessado no desenvolvimento?

Navegue pelo código, dê uma olhada no repositório SVN ou assine o registro de desenvolvimento via RSS.

Registro de alterações

Para obter mais informações, consulte lançamentos.


  • Introduces the Constant Contact integration module.
  • Updates the reCAPTCHA module to support reCAPTCHA v3.
  • Adds Dark Mode style rules.


  • Fixes the inconsistency problem between get_data_option() and get_default_option() in the WPCF7_FormTag class.
  • Suppresses PHP errors occur on unlink() calls.
  • Introduces wpcf7_is_file_path_in_content_dir() to support the use of the UPLOADS constant.


  • Specifies the capability_type argument explicitly in the register_post_type() call to fix the privilege escalation vulnerability issue.
  • Local File Attachment – disallows the specifying of absolute file paths referring to files outside the wp-content directory.
  • Config Validator – adds a test item to detect invalid file attachment settings.
  • Fixes a bug in the JavaScript fallback function for legacy browsers that do not support the HTML5 placeholder attribute.
  • Acceptance Checkbox – unsets the form-tag’s do-not-store feature.


  • CSS: Applies the “not-allowed” cursor style to submit buttons in the “disabled” state.
  • Acceptance Checkbox: Revises the tag-generator UI to encourage the use of better options in terms of personal data protection.
  • Introduces wpcf7_anonymize_ip_addr() function.
  • Introduces the consent_for:storage option for all types of form-tags.


  • Added the Privacy Notices section to the readme.txt file.
  • Updated the Information meta-box content.
  • Use get_user_locale() instead of get_locale() where it is more appropriate.
  • Acceptance Checkbox: Reset submit buttons’ disabled status after a successful submission.


  • Fixed incorrect uses of _n().
  • Config validation: Fixed incorrect count of alerts in the Additional Settings tab panel.
  • Config validation: Fixed improper treatment for the [_site_admin_email] special mail-tag in the From mail header field.
  • Acceptance checkbox: The class and id attributes specified were applied to the wrong HTML element.
  • Config validation: When there is an additional mail header for mailboxes like Cc or Reply-To, but it has a possible empty value, “Invalid mailbox syntax is used” error will be returned.
  • Explicitly specify the fourth parameter of add_action() to avoid passing unintended parameter values.
  • Check if the target directory is empty before removing the directory.


  • Additional settings: on_sent_ok and on_submit have been removed.
  • New additional setting: skip_mail
  • Flamingo: Inbound channel title changes in conjunction with a change in the title of the corresponding contact form.
  • DOM events: Make an entire API response object accessible through the event.detail.apiResponse property.
  • HTML mail: Adds language-related attributes to the HTML header.
  • File upload: Sets the accept attribute to an uploading field.
  • Introduces the WPCF7_MailTag class.
  • Allows aborting a mail-sending attempt using the wpcf7_before_send_mail action hook. Also, you can set a custom status and a message through the action hook.
  • Acceptance checkbox: Allows the specifying of a statement of conditions in the form-tag’s content part.
  • Acceptance checkbox: Supports the optional option.
  • New special mail tags: [_site_title], [_site_description], [_site_url], [_site_admin_email], [_invalid_fields], [_user_login], [_user_email], [_user_url], [_user_first_name], [_user_last_name], [_user_nickname], and [_user_display_name]
  • New filter hooks: wpcf7_upload_file_name, wpcf7_autop_or_not, wpcf7_posted_data_{$type}, and wpcf7_mail_tag_replaced_{$type}
  • New form-tag features: zero-controls-container and not-for-mail