What is the difference between ACF and WPUF in case of custom fields?

Hello @dicki

ACF allows you to add extra content fields to your WordPress edit screens, I mean, when you edit the post in the backend. These extra content fields are more commonly referred to as Custom Fields.

On the other hand, WPUF offers custom fields as well with the form builder. If you create custom fields with WPUF, it’s being saved with the posts in the backend.

But, ACF doesn’t offer you to create a frontend form for those custom fields, it just creates fields in the backend post editor.

I found people create custom fields using ACF and take input for those custom fields from the user using WPUF form by mapping the fields with meta_key. I really don’t know why they do it where WPUF offers both! Maybe, ACF offers some extra fields than WPUF? Or something I don’t know!

Hello @mehedi Hasan,

Thanks for your clear answer.
This makes me think of using WPUF only at the moment ??
But what i find out was this:

Custom fields made with WPUF will NOT show up ad the backend editor as far as i could see.
Custom fields made with ACF DO show up in the backend editor.
So i think that is the difference ??
So the combination of both seems a great combination.
So maybe i will use both ??
Sometimes it is hard to choose ??

Thanks anyway for you clear answer.

Hello @dicki

Let me make it easy for you!

WPUF custom fields show on the backend with the post actually, as you can see on this screenshot-> https://prntscr.com/nng3dv

I hope this will clear your confusion and help to take the decision ??

Thanks

If you define your custom fields with WPUF, you are married to WPUF.

If you define your custom fields with ACF, you are free to use other front end form plugins (USP, Gravity,…)