# Receiving and storing pictures

**URL:** https://community.thunkable.com/t/receiving-and-storing-pictures/1710149
**Category:** Questions about Thunkable X
**Created:** [February 1, 2022, 9:54pm UTC](https://community.thunkable.com/t/receiving-and-storing-pictures/1710149 "2022-02-01T21:54:10Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![lavrynenko](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/lavrynenko/32/108213_2.png) [@lavrynenko](https://community.thunkable.com/u/lavrynenko)
#### Post date: [February 1, 2022, 9:54pm UTC](https://community.thunkable.com/t/receiving-and-storing-pictures/1710149/1 "2022-02-01T21:54:10Z")

</div>

Friends, I ask for collective help - I just don’t know what to do.

There is an application that stores user data in a Google spreadsheet (username, city, phone number, etc.). You need to add the functionality of adding a user photo to the application.  
The question immediately arises:

1. Where to store the received photos?  
If you know the answer to this question - please tell me in as much detail as possible, at the “For dummies” level 🙂
2. How to split the storage of received photos in relation to the user? Those. user 1 - his photo is like this. And user 2 - his photo is like this.

Thanks in advance for your collective help. My brain is boiling.

Please do not ask why user data is now stored in a Google spreadsheet. Made due to lack of experience, but redoing it will be very long and very difficult.

As an option - to implement the storage of photos on an FTP server. But just a question:  
How to upload photos to the server? I don’t represent it at all.

---

<div class="post-metadata">

### Author: ![jared](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jared/32/138473_2.png) [@jared](https://community.thunkable.com/u/jared)
#### Post date: [February 1, 2022, 10:03pm UTC](https://community.thunkable.com/t/receiving-and-storing-pictures/1710149/2 "2022-02-01T22:03:00Z")

</div>

I

> [@lavrynenko](#):
>
> please tell me in as much detail as possible, at the “For dummies” level 🙂

instead of an answer I have a question. Is it a requirement of the project to store the photos locally? If not you simply need to reference the cell in which the image lives. This should return a URL that represents the image. This solution assumes the image already lives inside of the Google sheet.

Alternatively, you can upload the user image to cloudinary and then save the URL returned from cloudinary to Google sheets using the camera and mediaDB blocks. This will return a URL that represents the uploaded image and you can use the URL instead of a file to set an image

---

<div class="post-metadata">

### Author: ![muneer](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/muneer/32/75210_2.png) [@muneer](https://community.thunkable.com/u/muneer)
#### Post date: [February 2, 2022, 10:35am UTC](https://community.thunkable.com/t/receiving-and-storing-pictures/1710149/3 "2022-02-02T10:35:49Z")

</div>

Hello @lavrynenko  
The profile picture is now regarded as the standard in nearly all apps and when I think of building an app that stores users’ profile, I would like to include the picture.

One easy way is to use the cloudinary component in Thunkable to upload the picture of the user and obtain the URL from the `cloudinary Media DB` component. Store the URL in your `Data source` so you can always retrieve it to display it in your screen.

Should you do not want to use the cloudinary then you have other options which would require extra programming to achieve it.

Personally, I use `Firebase Storage` to save pictures and other files.

See this sample photo

```auto
https://firebasestorage.googleapis.com/v0/b/sample-structure-9d875.appspot.com/o/remote-control.png?alt=media&token=2a9c7d37-649d-47af-bd7b-2bf4f807fa1b

```

---

<div class="post-metadata">

### Author: ![lavrynenko](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/lavrynenko/32/108213_2.png) [@lavrynenko](https://community.thunkable.com/u/lavrynenko)
#### Post date: [February 2, 2022, 7:13pm UTC](https://community.thunkable.com/t/receiving-and-storing-pictures/1710149/4 "2022-02-02T19:13:29Z")

</div>

Interesting!  
It remains to understand how to implement all this in cloudinary… 🙂

---

<div class="post-metadata">

### Author: ![lavrynenko](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/lavrynenko/32/108213_2.png) [@lavrynenko](https://community.thunkable.com/u/lavrynenko)
#### Post date: [February 2, 2022, 7:15pm UTC](https://community.thunkable.com/t/receiving-and-storing-pictures/1710149/5 "2022-02-02T19:15:27Z")

</div>

> [@muneer](#):
>
> `https://firebasestorage.googleapis.com/v0/b/sample-structure-9d875.appspot.com/o/remote-control.png?alt=media&token=2a9c7d37-649d-47af-bd7b-2bf4f807fa1b`

As far as I understand from your example - we are talking about a picture. Is it possible with the method you described to implement:

1. Uploading a photo from the user’s device
2. Getting the URL of the uploaded image  
?

---

<div class="post-metadata">

### Author: ![muneer](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/muneer/32/75210_2.png) [@muneer](https://community.thunkable.com/u/muneer)
#### Post date: [February 2, 2022, 7:35pm UTC](https://community.thunkable.com/t/receiving-and-storing-pictures/1710149/6 "2022-02-02T19:35:02Z")

</div>

> [@lavrynenko](#):
>
> Is it possible with the method you described to implement:

Yes,  
I just made a sample demo for another member to read the file from user’s device and convert it to Base64 string.

See the demo in this post

> [@Upload images to Cloudinary using Web Api, only,](https://community.thunkable.com/t/upload-images-to-cloudinary-using-web-api-only/1701875/9):
>
> When you have the Base64 string and you store it in any kind of storage then viewing it is as simple as retrieving the string and assigning it to an image component because it accepts Base64 directly to be the image to display. This way, you store the Base64 in the table and you do not need to convert it to image again. I made a quick demo for you. See this project [https://x.thunkable.com/projectPage/61f68431c3761001dba12df1](https://x.thunkable.com/projectPage/61f68431c3761001dba12df1) In this demo it just reads the Base64 and assign it to an image a…

This is another demo to save `Canvas` image to Google drive  
[https://x.thunkable.com/projectPage/618cfa678cdb0f0011998dbe](https://x.thunkable.com/projectPage/618cfa678cdb0f0011998dbe)

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/0/f/0f59f292712368bce16ff80133ae10de8a6f27e8.png) [@system](https://community.thunkable.com/u/system)
#### Post date: [May 3, 2022, 7:35pm UTC](https://community.thunkable.com/t/receiving-and-storing-pictures/1710149/7 "2022-05-03T19:35:36Z")

</div>

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