I'll move this to GD&D as it is very much
on topic for this community!
I want to work on images, code and other stuff on different devices (pc or laptops) but i want to be able to access the files / source code across all devices.
So the solution is to use a cloud service right?
No, at least not if "cloud service" means "cloud drive" such as Dropbox. It is heavily recommended
not to put your working folder in a cloud drive, as this can cause complications on a file system level. Files may be locked while a cloud service is syncing them, which can lead to disruptions in the IDE, ranging from extended load times, crashes, deadlocks where both the IDE and the cloud are waiting for each other to release a lock, newer files being overwritten with older ones from the cloud due to a failed or delayed sync on your other devices up to, in the worst reported cases, outright project corruption due to interrupts and only parts of files being written.
Don't let two processes mess with the same file at the same time - that goes for any software.
it needs to work with no coding files like images too
Those are not causing any problems with source control. The answer remains unchanged.
While source control repositories can also be hosted in the cloud (or on a local server - which can be one of your devices), it is not a cloud drive in the "real time sync" sense. Source control is not affected by the issues I explained above because every sync, whether upstream or downstream, is an explicit action invoked by the developer, not some background process that does it whenever it feels like it. This means that, unless you intentionally try to provoke it or disregard telltale signs that file access is ongoing (such as saving/loading of the project or compilation), there won't be any access conflicts resulting in consequences like in the examples I outlined above.
Source control grants you immeasurably more benefits (what Mercerenies listed is only a small portion) than just allowing you to decentralize your workstation, not to mention being industry standard that should be common practice for any serious developer in the field as it is widely used across the world, anyway.
The current de facto standard source control solution is Git. Take a look at
what Git is about - maybe you'll find that it is to your liking.