News

Instagram Stories no longer allows you to create Boomerang with Live Photos

Table of contents:

Anonim

Instagram prevents you from boomeranging with Live Photo

If you didn't know, until recently we could create Instagram Stories, with a Boomerang effect, based on our Live Photo En something that many users used since it was very easy to create funny videos from these types of photographs of iOS

This was fixed in June 2020. We can now go back to creating Boomerangs with Live Photo.

If it is not a bug of the last released version (124.0), which we hope is the case, it seems that the platform wants us to use its Boomerang function directly to upload this type of content. Short videos with repetitive movements that always look good in our stories. We think this because they have added three new boomerang effects at the same time that they have removed the feature that gives this news its title.

This is how Instagram Stories with the Boomerang effect were shared with Live Photo:

We share the following video with you so you can see how easy this action was. We also pass it on so that you know how to do it, just in case it was a bug in the latest update of Instagram and in future versions allow it again:

It was a very interesting tip. Now it is not possible and the only way to make your Live Photo become a Boomerang post in Instagram stories, is by using a third-party app.

We have tried to find a way to do it but it is not possible. We have even created images with a rebound effect to later upload them to our Stories and it won't let us. When we upload it and edit it in the stories, it does the Boomerang movement but then, once published, it doesn't. If you want to try to do it yourselves here we pass you the video with which we teach you how to create this bounce effect with the Live Photo.

The Giphy app allows you to create GIFs with these types of images. You can access that app and easily create a Gif, which you can then share to your stories.

We hope that the next Instagram update will correct this supposed "bug" and, if it's not an error in the app, we'll find the fastest alternatives to perform this action.

Greetings.