GIMP online: browser options, file saving and privacy

Check which application you are opening, where its files live and how to retrieve a layered project before committing to an online edit.

Four matte prints with a cactus and blue mug photograph, garden and coast scenes, and a grey back card on cream paper.

You can use GIMP in a browser through a third-party host such as rollApp or OffiDocs, but GIMP's official releases are desktop applications. Check the host's saving conditions before editing: opening the program and getting your work back are separate parts of the job. I'd use a hosted session for a small, non-private task when installation isn't possible; for a layered project that needs repeated revisions, I'd choose desktop GIMP and keep the XCF on my own storage.

Choose actual GIMP or a different browser editor

If you need GIMP itself, start with a provider that explicitly runs the desktop application. If you only need a crop, a caption or a layered browser edit, a separate editor may do the job with fewer file-transfer steps. The name in a search result doesn't establish which application will open.

OptionWhat you're openingDecisive check
GIMP on rollAppA hosted GIMP application; its catalogue lists 2.10.34.Starter has read-only cloud access. Saving to connected storage or downloading through LocalSync requires Premium.
OffiDocs GIMP 2.10A hosted desktop GIMP route with an ENTER link to the provider's file manager.Find the assigned session folder and download both the project and export through File manager.
PhotopeaA separate editor running in your browser, with its own tools and document model.Its editable-project save format is PSD. Check the result rather than assuming a GIMP project will round-trip unchanged.
Official desktop GIMPThe project's packages for Windows, macOS and GNU/Linux.Installation must be allowed on the device. This gives you GIMP rather than a host's older session or a substitute editor.

rollApp and OffiDocs are service providers, not the GIMP project. GIMP's free-software licence doesn't make a host's computing, storage or download service free. Keep those two decisions separate: which application you need, then which service conditions you accept.

A browser extension is another separate product. The OffiDocs Chrome listing describes an integration with Linux desktop GIMP; its extension version number isn't the version of GIMP running remotely. A mobile app with a similar name is no stronger proof. The Google Play GiMP IMAGE EDITOR listing, for example, identifies a separate developer, Photo & Video Tools, and lists ads and in-app purchases.

Check the complete file transfer with a disposable sample

Before uploading an important image, make sure the provider can return the files you need. Use a non-sensitive sample and a new filename. This is a short acceptance check for your own session, not a reason to experiment on the only copy of a project.

  1. Check the save route and any required plan first. For rollApp, use the Premium/cloud-storage or Premium/LocalSync route below. For OffiDocs, identify File manager and the assigned folder before beginning.
  2. Upload or select the sample through the host. A file picker inside remote GIMP shows the remote computer's folders. Your laptop's Downloads folder won't automatically appear there.
  3. Open the image and add one identifiable layer. Give the layer a name such as Transfer check and put a visible mark on it. The purpose is to distinguish an editable project from a flattened picture when you reopen it.
  4. Save a working project as sample-transfer.xcf. Then export sample-transfer.png under a separate name, using the host destination described below. Don't overwrite the source image.
  5. Retrieve both files to storage you control. Wait for the downloads to finish, then locate the files on your own device or in the intended connected drive. A filename in a remote Save dialog isn't enough.
  6. Reopen and inspect them. Open the retrieved XCF in the GIMP version you intend to use next; confirm the named layer is separate and the edit is present. Open the PNG in an image viewer and check its dimensions and appearance. If either file is missing or wrong, resolve that before the real edit.

GIMP's Save and Export commands serve different purposes. XCF keeps the working structure, including layers, but doesn't preserve undo history. PNG and JPEG are finished image formats, not substitutes for the same editable layer stack. If the next device has no application capable of checking the XCF, keep the original and postpone a project-critical edit until that check is possible.

rollApp file picker at /home with the LocalSync transfer folder highlighted.
Open LocalSync to find files uploaded through rollApp; saving there triggers a download with Premium. Open the rollApp LocalSync file picker at full size.

Use rollApp's documented upload and download route

The rollApp plan comparison separates free Starter access from Premium: Starter provides read-only access to connected cloud files; Premium provides full access. Its Starter and Premium explanation explicitly says Starter can't save changes or create new files in cloud storage. A successful launch doesn't remove that restriction.

For a local sample, rollApp's LocalSync instructions give this sequence:

  1. Start from the GIMP catalogue's Launch Online route. Complete the provider's account steps only if its plan and data handling fit your task.
  2. Use the Upload icon in the rollApp toolbar. Wait for the upload notification.
  3. Inside GIMP, choose File → Open, navigate to LocalSync and select the uploaded file.
  4. With Premium, save the XCF into LocalSync. Writing a file there triggers a browser download. Export the PNG to LocalSync too, then check that both downloads arrived.

Download before closing the application. The same instructions say uploaded LocalSync files are deleted when the application closes. LocalSync is a transfer folder, not the place to leave the only copy overnight. Saving an updated file there triggers another download; check which downloaded version you are keeping.

Connected storage is the other route. According to rollApp's file-handling guide, connected services appear as folders in the remote home directory, with default names such as MyGoogleDrive, MyDropbox, MyOneDrive or MyBox. Save the XCF and export into the intended folder with a plan that permits writing. Check the files in the storage service afterwards; don't confuse a connected-drive folder with LocalSync.

I wouldn't start a long retouch on Starter and assume a download workaround will appear later. Choose a permitted save route at the outset, or use an editor whose saving conditions suit the task.

Save into OffiDocs' assigned folder, then download

OffiDocs' launch page describes GIMP 2.10. Its Workspace Marketplace listing describes the Linux GIMP integration and labels that integration free of charge. Neither statement guarantees the exact version, available resources or storage conditions of every session.

The provider's file-manager tutorial explains the important boundary: save within the directory assigned to the session, then use the webpage's File manager to retrieve the file. That tutorial is older than the current landing page, so follow the folder assigned to your session rather than typing an old server path from a guide.

  1. Use the GIMP landing page's ENTER route and identify the provider's File manager.
  2. Upload the disposable sample through the file manager's file chooser. Confirm it appears in that session's file list before opening it in GIMP.
  3. Use GIMP's Save As for the XCF and Export As for the finished PNG. Put both in the assigned folder that File manager exposes.
  4. Return to File manager and download each file. Locate them outside the hosted session and perform the reopen check.

If a file saved in GIMP isn't visible in File manager, check the save directory before repeating the edit. The provider warns that a file saved elsewhere won't be accessible through that manager. Save a copy into the assigned location while the original session is still available.

OffiDocs tells free users to download their files, and its desktop-app privacy policy also describes inactivity-based deletion. Its documents give different inactivity periods, so I wouldn't build a recovery plan around a timer. Retrieve the work before leaving and keep your own copies.

Check where the image goes before uploading

A hosted desktop processes the file on the provider's computer. OffiDocs' privacy policy explicitly describes remote storage and says data travels through OffiDocs and Google Drive servers when that integration is used. That's a different arrangement from ordinary editing of a local file in a browser-native application.

Choose the route before sending private photographs, client material or documents covered by an organisation's policy. Check the provider, storage destination, deletion controls and permission request. If the job requires files to stay on your own device, use a suitable local workflow rather than uploading first and investigating afterwards.

Read extension and Drive permissions separately. The OffiDocs Chrome extension disclosure says it reports browsed webpages to its servers to scan for image files; a checkbox in the extension popup can disable that scanning, with reduced functionality. The Workspace listing instead requests access to the specific Drive files used with the app, plus account email and personal information. These are different access surfaces. A free listing or a familiar product name isn't a privacy guarantee.

Photopea offers an alternative for a browser edit: its privacy policy describes processing opened files on your device and explains optional cloud-storage transfers separately. Check the handling of any extra online or AI feature before sending an image to it. That policy statement isn't a guarantee about every embedded copy, extension or similarly named service.

Match the version and file format to the next edit

The rollApp catalogue lists GIMP 2.10.34, while OffiDocs advertises 2.10. A current GIMP 3 tutorial can therefore show different tools or editing behaviour. Check the supplied application version before relying on a feature; a host won't gain a newer feature because the tutorial includes it.

For a GIMP-specific project, check the parts that matter: layer order, masks, editable text, effects and required plug-ins. Keep an untouched XCF before transferring between versions or editors. A file opening successfully proves less than being able to change the required layer and save it for the next person. Don't flatten the project merely to make a transfer appear successful.

Photopea's opening and saving instructions use File → Save as PSD for an editable document and File → Export As for a finished image. If you switch editors, retain the original XCF separately and check the PSD's relevant structure when reopened. PNG is suitable for handing over the visible image; it doesn't carry the same editable project.

GIMP plug-ins also belong to a particular version and environment. Before choosing a hosted session for a plug-in-dependent task, verify that the required plug-in is present and permitted there. Installing a browser extension isn't the same operation as adding a GIMP plug-in to a remote Linux installation. For desktop work, the separate guide to GIMP 3 plug-in installation and older plug-in compatibility covers that task.

On a phone or tablet, try the complete selection, text-entry and download sequence with the sample before a detailed edit. Photopea itself recommends a larger screen, precise pointing device and keyboard for comfort. The same practical check is useful for a remote desktop: being able to display its window doesn't establish that the controls suit a careful mask edge.

Fix file and session problems without losing the work

SymptomCheck and next action
Your local picture isn't in File → OpenYou're looking at remote folders. Use the host's upload route or connected storage. In rollApp, uploaded local files appear in LocalSync.
GIMP opens but won't save the resultCheck the plan and write permission first. rollApp Starter can't write to connected cloud storage; LocalSync saving also requires Premium.
OffiDocs saved a file but File manager can't find itCheck the assigned folder. Save a copy into the location exposed by File manager before ending the session.
No rollApp download appearedCheck that the output was written to LocalSync with Premium and inspect the browser's download status. Preserve the session until you have a retrieved copy.
Only a flat picture came backCheck the extension and save command. Retrieve the XCF as well as the PNG/JPEG. Renaming a PNG to .xcf won't restore its layers.
An expected tool or plug-in is missingCheck the host's GIMP version and installed components. Keep your files and move to a compatible environment rather than replacing project structure blindly.
The session feels delayed or disconnectsProtect the latest saved/downloaded copy first. Use the small sample to separate a general connection/session problem from a demanding document. Don't refresh a tab containing the only unsaved work as the first troubleshooting step.

For a large composite, repeated masks or a task tied to current GIMP features, my default is the official desktop application. The reason is control of the working files and editing environment, not a promise that every browser editor is slow. If installation is blocked, choose a permitted browser route and complete the sample transfer first. Start the real image only when the editable project and finished export can both reach their intended destination.

Elena Morris

Elena Morris

Elena Morris is the GIMP image-editing and compositing editor at TheGIMP.net. She writes about selections, masks and layers, restrained retouching, compositing and export.