With a single focus, prepare your images for sharing. Upload, edit, arrange and share still photos with ease. Whether you are preparing screenshots, processing a small group of images, or refining an individual photo, choose the link that best suits where it will go.
Explore the upload, review, organization and editing steps, with clear notes on supported formats, link behavior and image privacy.
Start with a file, a drop or an image pasted from the clipboard.
Choose a page designed for a person or image bytes designed for an embed.
Handle a small group without losing the relationship between a file and its result.
Organize your images so the next edit or handoff starts from a useful record.
Make a new derivative while keeping the uploaded source available.
Exercise per-image rules on both the share page and image-byte route.
Understand how a processed image differs from its original and which details can still be visible.
Iterate without silently replacing the image you started with.
These product captures use generated sample images to show actual upload results, link choices and batch controls.
Captured with generated sample imagery to show returned dimensions and the two different link types.
See screenshot upload ↗
Captured with generated sample images. Each row keeps its filename with the result before export.
See batch upload ↗The uploader will accept any image file that is a still (not animated) image in one of the following formats: JPEG, PNG, WebP or AVIF. Each image may not exceed 10 MB in size. The AVIF format must use the AV1 image codec supported by the decoder. SVGs (scalable vector graphics) cannot be accepted as they are active document formats. Animated images will be rejected rather than flattened without notification.
Before being decoded, the request has a bounding limit. After decoding, the server verifies the format of the decoded request and the pixel limits. If necessary, it adjusts the orientation of the request and then re-encodes it. The description presented in the interface refers to the re-encoded version of the image, rather than the original file. When an image is re-encoded, there may be changes to the way the image was compressed or how colors are represented. Therefore, if these differences matter to you, you should retain your original image.
Browse for an image, drop a supported file, or paste image data from the clipboard. A selection above the batch limit is trimmed to the supported count with a notice.
The server checks the actual image content and dimensions instead of trusting the filename alone. Corrupt, unsupported, animated or oversized files receive an error.
Check the final filename, format, pixel dimensions and stored byte size. The queue shows each result separately, so a failed item does not hide a successful one.
The share page URL will open a small window above the image so that users have a sense of where they are in relation to the file and have a consistent way of accessing it. On the other hand, the direct image URL will return the actual image representation of the file. This is exactly what the HTML image tag and Markdown renderer require.
When a user types in a share-page URL they will be directed to an HTML page that allows them to view your shared content. When a user enters a direct-image URL they will receive image data which can then be used to create an embedded version of the image. You should check if the person you want to send your link to has access to that specific link before you share it, and you should make sure that the permission settings are correct.
| Destination | Share-page URL | Direct image URL |
|---|---|---|
| Human review | Useful: shows a page with filename and image | Opens only the image; little context |
| Markdown or HTML embed | Usually wrong: this is an HTML document | Correct form when publicly reachable and permitted |
| Recipient access | Requires access to view the page | Requires access to retrieve the image bytes |
| Password or expiry policy | The server checks the share state | The image-byte route checks the same share state |
Once signed in, you will be able to view all images uploaded to your account. In addition, the library includes features such as searching for files using their names, sorting files based on when they were uploaded, alphabetically, or by how much space they take up. Additionally, you may create and manage collection(s) of images; tag images; view information about each image; and find out how many times an image has been used.
Bulk selection will allow you to tag images, move images to different collections, or place images into Trash. Images that have been placed into Trash may still be retrieved. When you move an image into Trash, it is no longer visible in your active library, however the actual image data is still stored on your computer.
Open an owned image and keep its original record.
Crop, adjust or add reviewed annotation layers.
Check dimensions, format, legibility and privacy.
Name, tag or move the new image into a collection.
A user can select by dragging over the crop area, as well as enter the exact coordinates of the upper left corner (left), upper right corner (top), width, and height. In addition, there are several output options available: width and height; quarter-turn rotation; horizontal and vertical flips; PNG/JPEG/WebP format; and output quality. There are also many editing tools available to the user, such as straighten; brightness; contrast; saturation; blur; sharpness; and five different filters (original, monochrome, vivid, warm, and cool).
Annotations are separate layers used when creating. Types of layers include: text; rectangles; circles; arrows; frames; stickers; freehand strokes; textures; bounded blur or pixelated areas; and images from your own library. You may create, select, reorder, hide, duplicate, or delete layers. Both image controls and layer modifications are covered by undo and redo.
A share may include a password, expiration date, or revocation condition. Both the viewing page and direct access to an image should be subject to access control. A password or expiration date does not allow for recovery of a downloaded or stored copy.
Only use access control after determining how the controls affect the image and preview of the image. When an expiration date is applied to a request made for an item from a service, that item will be unavailable to anyone who attempts to request it at a later time. However, setting an expiration date does not ensure that no copies of the item have been downloaded, nor does it ensure that all caches containing responses to previous requests for the item have purged those responses.
Share-page request or direct image request.
Evaluate revocation, expiry and any scoped password grant.
Return the page/image only when the local policy permits it.
The processed image might differ from the original image in terms of format, dimensions (width and height), how colors are managed, and possibly in any included metadata. It is recommended that you retain a copy of the original image if the exact byte sequence of that image is critical. Before you use the processed image, examine the file provided by the system.
Re-encoding will strip away some of the metadata associated with the original file; however, re-encoding will not mask the identity of people, their faces, where they live, etc. that are contained within the image. If you need to make sure this information is hidden, then use a metadata viewer to examine the newly encoded file.
A direct image URL can be used when the destination can fetch the image bytes and access is permitted. Test the response in the destination before publishing it.
The current uploader accepts JPEG, PNG, WebP and AVIF still images up to 10 MB each. Animated formats and SVG are rejected. The editor exports PNG, JPEG or WebP.
Yes. Save edited work as a new library item so the original remains available for comparison.
A blur or pixelation layer changes the saved copy, but review the full image at its intended size. Other identifying details can remain outside the edited region.
Password and expiry settings can restrict future requests when both the viewer page and image route enforce them. Check how the access rule works before relying on it for sensitive material.
No. Expiry prevents later requests that reach the application from being allowed under the expired policy. It does not delete the stored object, recall a download or guarantee removal of every cached copy.