Element Exists vs Image Exists

Help Activities
, ,
1

Hi,
Of both these activities Which one takes more time? Element Exists (for a UI window with selector) or Image Exists (for a UI Element like a Cancel button). Which one is recommended?

Thank you,

2

@A_Learner

Recommended is to use element exists only over image exists…

At any given point of time selectors are more reliable than using image activities

And being fast dependa on factors…

If that oage is heavy the selector might be slow given that the resolution of the image matches exactly with the image provided in image exists…which is rare again

So preferrably use element exists if that is supported

Cheers

1 Like
3

Hello @A_Learner Welcome to the UiPath Community Forum

I agree with @Anil_G, that Element Exists is more reliable than Image Exists. Why - that is a different topic for discussion because Element Exists → It verifies whether the selector is present in the properties of application(type, class,id,aaname) or not where Image Exists → it verifies the presence and absence(image).

To verify the speed, I used the attached sample workflow which simply opens Edge Browser → www.google.com and check for the finder( :mag:) element.

Execution Log:
Capture-2

Sample Workflow:
Main.xaml (17.5 KB)

may need to adjust some references.

Thanks.

4

Hi A_Learner,
You can use Check App State activity intead of Element Exists of Image Exists activities. This activity is faster and reliable. If you decide to use this activity, please configure the properties as follow:

  • Visibility check = none
  • Wait for page load = none
  • Targeting method = Strict Selector (Only check the Strict Selector checkbox).
  • Timeout = Default values is 5 Seconds, you can modify it according to your needs.

Cheers!

1 Like
5

Hi @A_Learner

The time it takes for either “Element Exists” or “Image Exists” in UiPath depends on factors like the complexity of the UI and the size of the image. Generally, “Element Exists” is preferred over “Image Exists” because it directly checks for the presence of a UI element based on selectors, which is more reliable and efficient than image recognition. Using selectors is less prone to changes in the UI layout.

However, the actual performance may vary based on specific scenarios, so it’s advisable to test both methods in your context and choose the one that provides better results for your particular automation process.

Hope you understand!!
Regards

1 Like
6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.