# How to make a good trackable image for augmented reality

Image recognition is based on the number of key points that the platform can detect in the uploaded image (marker). The more points, the faster and more stable the tracking will be.

A good marker has the following features:

► **High contrast**_**.**_ The difference between tones helps to detect more key points in an image.

· An example of a _bad_ marker:

<figure><img src="https://3462873876-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIqwMMglOZIuMlGrpgPV1%2Fuploads%2FnqpdfPDXwRADSsa9uwjP%2Fimage.png?alt=media&#x26;token=edd5b442-9446-478a-96b8-a28bcb12a6ed" alt=""><figcaption></figcaption></figure>

It’s hard to distinguish different details in the picture above because of a small range of tones. There are no bright highlights or dark shadows. Everything is in shades of grey.

· An example of a _good_ marker:

<figure><img src="https://3462873876-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIqwMMglOZIuMlGrpgPV1%2Fuploads%2FOfHeJIBK1qxFjBRGqitk%2Fimage.png?alt=media&#x26;token=152ebb96-61c1-43f1-b585-97fce01c253d" alt=""><figcaption></figcaption></figure>

This picture shows a wider range of tones. The object in the image stands out of the background.

► **No repeating shapes or patterns**. Identical or similar objects have a negative effect on recognition and tracking.

· An example of a _bad_ marker with many identical shapes and patterns:

<figure><img src="https://3462873876-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIqwMMglOZIuMlGrpgPV1%2Fuploads%2Fo0eEpOWxxeIc9nRR5rgx%2Fimage.png?alt=media&#x26;token=3eb8cfd5-99a8-4508-ba69-47ea9864696a" alt=""><figcaption></figcaption></figure>

This image has many corner points, but they are repetitive and absolutely identical, therefore the tracking will be unstable as the points will get mixed up with one another. It is better not to use an image like this.

► **Lots of details**. The more unique elements in an image, the better it is recognised.

· An example of a _good_ marker with lots of details:

<figure><img src="https://3462873876-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIqwMMglOZIuMlGrpgPV1%2Fuploads%2FYRG7haPiudmZBoUNLmrn%2Fimage.png?alt=media&#x26;token=6abf13a0-eb77-4bbf-bed5-dae076f6747b" alt=""><figcaption></figcaption></figure>

► **Even distribution of key points**_**.**_ Good image tracking requires that key points are evenly distributed throughout the image.

· An example of a _bad_ point distribution:

<figure><img src="https://3462873876-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIqwMMglOZIuMlGrpgPV1%2Fuploads%2FTBOc6tyPBVKV9a4vGwQH%2Fimage.png?alt=media&#x26;token=ef562ad9-db57-49c9-8238-5dbf28598243" alt=""><figcaption></figcaption></figure>

Most of the points are gathered in one corner of the image, which will have a negative effect on tracking. There are some ways to avoid this without changing the marker. You can crop the image or add additional elements so that most of the points are not located in one corner of the marker, but are distributed throughout the whole image.

\
· An example of a _good_ point distribution:

<figure><img src="https://3462873876-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIqwMMglOZIuMlGrpgPV1%2Fuploads%2FPlXMIEEmFsQqD7WAxOXY%2Fimage.png?alt=media&#x26;token=6c298c7e-2c86-427f-b286-38e08c9e2451" alt=""><figcaption></figcaption></figure>

► **Square and angular shapes**. They have more key points than round objects. Round shapes are smooth without sharp transitions, so the image will be difficult to identify.

· Example of a _bad_ shape:

![](https://3462873876-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIqwMMglOZIuMlGrpgPV1%2Fuploads%2FarccNBWWrp5e9bnSxv4I%2Fimage.png?alt=media\&token=c6260b37-2c78-4f9a-bcb6-3c8b43a590fe)

Here we can see the shape without sharp lines. Such an image will be hard to detect.

\
· Even though a square has 4 corners, which are easy to detect... such a shape is not used for one reason — the square is symmetric, so it becomes impossible to determine its orientation in space. If you turn the square by 90º, nothing changes. That’s why it’s better not to use this figure as a marker.

![](https://3462873876-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIqwMMglOZIuMlGrpgPV1%2Fuploads%2FkonHMn295BZw3Vfb00vB%2Fimage.png?alt=media\&token=9216577b-5d04-42e2-87e7-7f106c97bf44)

· An example of a _perfect_ shape is a triangle.

![](https://3462873876-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIqwMMglOZIuMlGrpgPV1%2Fuploads%2FVI6asK999aavKVFx1Slq%2Fimage.png?alt=media\&token=e6c09d41-d7eb-4c4e-bf54-21af8e7ea0a3)



► **The Feature — Exclusion Buffer**\
If you look again at the images above, you will see that the points don’t fill the whole marker... About 8% of image stays unoccupied. (Even though there are objects in this area that can be detected). This area is an exclusion buffer.  Point recognition doesn’t happen in this area.

You can avoid this situation by adding a white frame to the marker (about 8% of the width). The images below show an example of a _bad_ marker and a _good_ marker.

\
· _Without a frame,_ precious information is lost. Some points are close to the edge of the marker.

<figure><img src="https://3462873876-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIqwMMglOZIuMlGrpgPV1%2Fuploads%2FLd8LbB5GMxk876BSlhBZ%2Fimage.png?alt=media&#x26;token=5bf053ee-c784-4402-9137-9d1b1056a2c7" alt=""><figcaption></figcaption></figure>

· _With a frame_, the information stays within the borders of the marker.

<figure><img src="https://3462873876-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIqwMMglOZIuMlGrpgPV1%2Fuploads%2FWSPbsSJtWJMG7IwN4S9S%2Fimage.png?alt=media&#x26;token=32beed97-7677-49f3-bae3-55dd7fc47972" alt=""><figcaption></figcaption></figure>
