> ## Content Index
> Fetch the complete content index at: https://blog.esadax.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# PictShare
- URL: https://blog.esadax.com/en/pictshare-en-6/
- Published: 2026-11-15T04:54:01.000Z
- Updated: 2026-11-15T04:54:01.000Z
- Author: Esadax 
- Tags: #tr-apps-03-catalog-pictshare, #en, #mdx-imported, Apps

# What is PictShare?

PictShare is a lightweight, open-source, self-hosted file-sharing platform designed for uploading, storing, transforming, and sharing images, videos, audio files, and text snippets.

It provides a centralized web interface and upload API that allow users and applications to publish files and obtain shareable URLs without depending on external file-hosting services.

Unlike traditional cloud storage platforms, PictShare focuses on simple file hosting and media delivery. Users can upload content, generate direct links, transform images through URL parameters, and share files with others.

One of its distinguishing features is its URL-based image processing system. Users can resize, rotate, and apply filters to images by modifying their URLs, without manually creating multiple versions of the original file.

PictShare also supports video processing, GIF conversion, text hosting, Markdown rendering, audio playback, and shareable media albums.

Its file-based architecture does not require a conventional database, making it particularly suitable for homelabs, developers, and organizations that need a compact file-sharing service.

## History of PictShare

PictShare is an open-source project developed by HaschekSolutions.

The project was created to provide a self-hosted alternative to public image-hosting services, with an emphasis on simplicity, flexibility, and control over uploaded content.

The application evolved from a basic image-hosting service into a broader media-sharing platform supporting images, videos, text snippets, external storage, and API integrations.

PictShare version 3 introduced a significant architectural rework, including an updated REST-oriented API, additional content types, external storage support, albums, and a built-in Model Context Protocol (MCP) server.

The project is primarily implemented in PHP and provides Docker-based deployment.

## Key Features of PictShare

PictShare provides several features for uploading, managing, transforming, and sharing files.

- **Image Hosting:** Upload and share images through direct URLs.
- **Video Hosting:** Upload and distribute supported video formats.
- **Text Hosting:** Store text snippets and make them available through shareable links.
- **Markdown Rendering:** Display uploaded Markdown files as formatted HTML.
- **Audio Hosting:** Support audio formats such as MP3, WAV, OGG, FLAC, and M4A.
- **URL-Based Transformations:** Resize, rotate, and apply filters to images directly through their URLs.
- **Automatic WebP Conversion:** Serve compatible images in WebP format when supported by the requesting browser.
- **GIF Conversion:** Convert animated GIF files into MP4 videos.
- **Video Processing:** Resize supported videos and generate preview images.
- **Duplicate Detection:** Reuse existing files when identical content is uploaded.
- **Upload API:** Integrate file uploads into scripts, applications, and automated workflows.
- **URL Importing:** Upload files by providing an accessible remote URL.
- **Shareable Albums:** Combine multiple uploaded files into a single gallery link.
- **File Deletion Codes:** Generate individual deletion codes for uploaded files.
- **External Storage:** Store files using S3-compatible services and other storage backends.
- **Storage Encryption:** Encrypt files stored through supported external storage controllers.
- **EXIF Removal:** Remove embedded EXIF metadata from uploaded photographs, including GPS coordinates and camera information.
- **MCP Integration:** Allow compatible AI agents to upload, retrieve, transform, and manage files.
- **Docker Support:** Deploy the application using an official Docker image.

## Use Cases

PictShare is suitable for individuals, developers, and organizations that need a simple file-upload and sharing infrastructure.

Common use cases include:

- **Image Hosting:** Upload screenshots, photographs, graphics, and other images.
- **Video Sharing:** Publish short videos and supported media files through direct links.
- **Application Upload Endpoints:** Provide a centralized destination for files generated by external applications.
- **Developer Workflows:** Share screenshots, logs, and development artifacts.
- **Technical Support:** Upload error screenshots and diagnostic files for support requests.
- **Text Sharing:** Publish configuration examples, code snippets, and technical notes.
- **Website Media:** Host images and optimized media for websites and applications.
- **Temporary File Distribution:** Share files through generated URLs and individual deletion links.
- **Documentation:** Host screenshots and other assets used in technical documentation.
- **Automation:** Integrate uploads into scripts, deployment workflows, and external services.
- **Homelab Infrastructure:** Operate a private alternative to public image and file-hosting services.

## Benefits of PictShare

- Lightweight, self-hosted file-sharing platform
- No conventional database required
- Supports images, videos, audio, and text
- Automatic image transformations through URLs
- GIF-to-MP4 and image-to-WebP conversion
- Simple REST-oriented upload API
- Remote URL importing
- Duplicate detection to reduce storage consumption
- Individual file deletion codes
- Optional master deletion controls
- S3-compatible external storage support
- Optional encryption for externally stored files
- Automatic EXIF metadata removal
- Docker-based deployment
- Built-in MCP server for AI agent integrations
- Greater control over uploaded files and hosting infrastructure

## How to Install PictShare

To install PictShare through Esadax, follow these steps:

1. Purchase the application through Esadax.
2. After purchasing, you will be prompted to provide the required configuration parameters.
3. Configure the public application URL using your domain or subdomain.
4. Configure persistent storage for uploaded files.
5. Set an upload code if uploads should require authentication.
6. Configure file-processing options when necessary.
7. Configure external storage if required.
8. Click **Deploy** to launch the application.
9. Access PictShare through its assigned application URL.
10. Upload a test image and verify that the generated URL works.
11. Test image transformations and file deletion.
12. Configure API integrations for applications that need automated uploads.

Once deployed, PictShare provides a centralized endpoint for uploading and distributing files.

## Image Upload and Sharing

PictShare provides a web interface for uploading images and generating shareable URLs.

After an upload is completed, the application generates a unique filename and makes the image available through its public URL.

The general workflow is:

1. Select an image from your device.
2. Upload the file through the web interface or API.
3. PictShare validates and processes the uploaded content.
4. The file is stored in the configured storage backend.
5. A unique URL is generated.
6. Share the URL with other users or applications.

PictShare also generates individual deletion codes that allow uploaded files to be removed without requiring direct access to the server's filesystem.

The same upload infrastructure can be used by external applications, scripts, and command-line tools.

## URL-Based Image Transformations

One of PictShare's most useful features is its URL-based image processing system.

Instead of manually generating multiple image sizes, users can request different versions of an uploaded image by modifying its URL.

Available operations include:

- Resizing images
- Rotating images
- Applying image filters
- Converting compatible images into WebP
- Generating placeholder images
- Creating identicons

For example, an uploaded image might be available at:

`https://files.example.com/image123.jpg`

A resized version can be requested using:

`https://files.example.com/800x600/image123.jpg`

Additional transformations can be combined in the URL.

PictShare version 3 requires the original filename to be the final component of the URL. This differs from older versions, which allowed the filename to appear elsewhere in the path.

This approach makes PictShare particularly useful for websites and applications that need multiple image sizes without maintaining separate copies of every image.

## Video Hosting and Processing

PictShare supports uploading and sharing video files through generated URLs.

The platform includes video-processing capabilities for preparing media for browser-based playback and distribution.

Video functionality includes:

- Uploading supported video files
- Generating preview images
- Resizing supported MP4 videos
- Converting incompatible video encodings when possible
- GIF-to-MP4 conversion
- Serving processed video through direct URLs

Video processing relies on FFmpeg.

For installations handling large videos or frequent conversions, sufficient CPU resources should be allocated to the application.

PictShare also supports a separate FFmpeg worker that processes queued conversion tasks, allowing resource-intensive operations to run independently of the main web request.

## Text Snippets and Markdown Hosting

PictShare is not limited to images and videos.

It also supports text hosting, allowing users to upload text content and distribute it through shareable URLs.

Common examples include:

- Source code snippets
- Configuration files
- Logs
- Technical notes
- Documentation excerpts
- Markdown documents
- Plain-text information

Markdown files can be rendered as formatted HTML, making PictShare useful for sharing lightweight documentation.

Text content can also be accessed through raw-data views or downloaded, depending on the supported content type and configuration.

This provides a convenient alternative to manually sharing text files or using external paste services.

## Audio Hosting

PictShare supports hosting audio files and providing a browser-based audio player.

Supported formats include:

- MP3
- WAV
- OGG
- FLAC
- M4A

Uploaded audio files can be accessed through generated URLs and played using compatible browsers.

This makes PictShare useful for sharing audio recordings, short sound clips, and other supported audio content.

## Albums and Media Galleries

PictShare provides an album feature for grouping multiple uploaded files into a single shareable gallery.

Instead of distributing separate links for every image, users can create an album containing several files.

Album functionality includes:

- Combining existing uploads into an album
- Generating a unique album URL
- Sharing multiple files through one link
- Presenting files in a gallery
- Creating collections of uploaded content

Albums are particularly useful for sharing screenshots, event photographs, collections of graphics, and other related media.

## Upload API and Developer Integrations

PictShare provides an HTTP API that allows external applications to upload files programmatically.

The API returns JSON responses containing information about the uploaded content and its generated URL.

A basic upload request uses the `/api/upload` endpoint.

Example using cURL:

```bash
curl -F "file=@image.jpg" \
  https://files.example.com/api/upload

```

A successful response contains information such as:

- Upload status
- Generated file hash
- File type
- Public URL
- Individual deletion code
- Deletion URL

PictShare also supports uploading content from remote URLs through its URL-import functionality.

Common integration scenarios include:

- Automatically uploading screenshots.
- Sending generated application images to a centralized endpoint.
- Sharing files from shell scripts.
- Integrating uploads into web applications.
- Uploading videos from automated workflows.
- Publishing logs and text snippets.
- Creating albums from multiple uploads.
- Managing files through external applications.

The API makes PictShare particularly useful for developers who need file-hosting functionality without implementing a separate upload infrastructure.

## Model Context Protocol (MCP) Integration

PictShare includes a built-in Model Context Protocol server.

MCP allows compatible AI applications and agents to interact with the file-sharing service through a standardized tool interface.

The endpoint is available at:

`POST /mcp`

Available tools include:

- **upload\_from\_url:** Download a remote HTTP or HTTPS resource and store it in PictShare.
- **upload\_base64:** Upload content encoded as Base64 or supplied as a data URI.
- **get\_file\_info:** Retrieve information about an uploaded file.
- **delete\_file:** Delete a file using its deletion code.
- **create\_album:** Group existing uploads into a shareable album.
- **transform\_image:** Generate URLs for resized, filtered, or rotated images.

When `UPLOAD_CODE` is configured, MCP clients must provide the upload code as a bearer token.

This integration is useful for automated workflows where AI agents need to upload screenshots, process media references, or manage files through a self-hosted service.

## External Storage and Encryption

PictShare supports external storage backends through its storage controller architecture.

This allows uploaded files to be stored outside the main application directory.

Supported configurations include:

- Local filesystem storage
- S3-compatible object storage
- MinIO
- FTP storage
- Additional storage controllers supported by the application

S3-compatible storage can be useful when hosting large media collections or operating multiple PictShare instances.

The application can also encrypt files stored through supported external storage controllers.

Encryption is performed automatically during uploads and downloads when the appropriate encryption key is configured.

This allows organizations to separate their application infrastructure from their media storage while maintaining additional protection for externally stored files.

## Duplicate Detection and File Management

PictShare includes duplicate detection to avoid storing identical uploads multiple times.

When an exact duplicate is uploaded, the application can reuse the existing stored file rather than creating another physical copy.

This helps reduce storage consumption when multiple users or applications upload the same content.

File management functionality includes:

- Unique file identifiers
- Individual deletion codes
- Optional master deletion controls
- File metadata retrieval
- Album organization
- External storage support
- Upload activity logging

The deletion code returned during an upload should be stored securely because it may be required to remove the associated file.

## Security / Administration / Configuration

PictShare is designed as a lightweight file-sharing service, so administrators should pay particular attention to upload permissions and the content being hosted.

Important security practices include:

- Enable HTTPS through a reverse proxy.
- Configure `UPLOAD_CODE` when public anonymous uploads are not required.
- Restrict uploads and administrative access using `ALLOWED_SUBNET` when appropriate.
- Use a strong `MASTER_DELETE_CODE` if global deletion functionality is enabled.
- Configure `MASTER_DELETE_IP` to restrict master deletion operations.
- Protect uploaded files and storage directories.
- Configure `TRUSTED_PROXIES` correctly when running behind a reverse proxy.
- Avoid exposing administrative functionality unnecessarily.
- Monitor storage consumption and upload activity.
- Use separate credentials for external storage.
- Protect encryption keys and configuration files.
- Keep the Docker image updated.
- Back up uploaded content regularly.

PictShare removes EXIF metadata during image uploads, helping prevent accidental publication of embedded GPS coordinates and camera information.

### Important Consideration: HTML Hosting

PictShare supports hosting raw HTML pages, but this functionality is disabled by default.

When enabled, uploaded HTML can execute arbitrary JavaScript on the same origin as the PictShare application.

This can expose visitors and authenticated administrative sessions to serious security risks.

Only enable HTML hosting when there is a clear requirement, and use a dedicated `HTML_UPLOAD_CODE` that is separate from the normal upload code.

For public file-sharing deployments, leaving HTML hosting disabled is strongly recommended.

## Best Practices for PictShare

- Use a dedicated domain or subdomain for uploaded files.
- Enable HTTPS for all external access.
- Configure upload authentication when appropriate.
- Set file-size limits at the reverse proxy.
- Monitor disk consumption and bandwidth usage.
- Use external object storage for larger media collections.
- Enable storage encryption when supported and required.
- Keep deletion codes secure.
- Restrict administrative access.
- Configure trusted proxies accurately.
- Avoid enabling HTML hosting unless necessary.
- Use allowed content types to limit unnecessary functionality.
- Include uploaded files in regular backups.
- Test restoration procedures.
- Keep the application and FFmpeg components updated.

## Configuration Parameters

After purchasing this application on **Esadax**, you will be prompted to provide the configuration parameters required by the deployment.

Esadax adds the supplied variables to the deployment so the application can be launched with the configuration it requires.

PictShare version 3 uses a configuration file named:

`inc/config.inc.php`

The repository also provides an example configuration file:

`inc/example.config.inc.php`

The following options are supported by the upstream configuration:

### Application and Access Settings

| Parameter            | Description                                                                                                          |
| -------------------- | -------------------------------------------------------------------------------------------------------------------- |
| URL                  | Public base URL used when generating links. Must end with a trailing slash.                                          |
| UPLOAD\_CODE         | Optional code required for uploads through supported API and upload requests.                                        |
| ALLOWED\_SUBNET      | Comma-separated IP addresses, CIDR ranges, or hostnames allowed to upload files and access the administration panel. |
| TRUSTED\_PROXIES     | IP addresses, CIDR ranges, or hostnames of trusted reverse proxies.                                                  |
| MASTER\_DELETE\_CODE | Optional master code allowing deletion of any stored file.                                                           |
| MASTER\_DELETE\_IP   | Restricts master deletion operations to specified clients.                                                           |
| LOG\_UPLOADER        | Enables logging of uploader IP addresses to /data/uploads.csv.                                                       |
| LOG\_VIEWS           | Enables request logging for debugging purposes.                                                                      |

### Image Processing Settings

| Parameter           | Description                                                                     |
| ------------------- | ------------------------------------------------------------------------------- |
| PNG\_COMPRESSION    | PNG compression level, from 0 to 9.                                             |
| JPEG\_COMPRESSION   | JPEG quality setting, from 0 to 100.                                            |
| WEBP\_COMPRESSION   | WebP quality setting, from 0 to 100.                                            |
| ALWAYS\_WEBP        | Serves compatible JPEG images as WebP when supported by the requesting browser. |
| CORS\_ALLOW\_ORIGIN | Configures the Access-Control-Allow-Origin response header.                     |
| FFMPEG\_BINARY      | Path to the FFmpeg executable used for media processing.                        |

### Content Type Settings

| Parameter              | Description                                                       |
| ---------------------- | ----------------------------------------------------------------- |
| CONTENTCONTROLLERS     | Optional comma-separated whitelist of supported content types.    |
| HTML\_HOSTING\_ENABLED | Explicitly enables raw HTML hosting. Disabled by default.         |
| HTML\_UPLOAD\_CODE     | Separate authorization code required for publishing HTML content. |

Supported content controller values include:

- `IMAGE`
- `SVG`
- `TEXT`
- `VIDEO`
- `URL`
- `HTML`

HTML hosting also requires `HTML_HOSTING_ENABLED` and `HTML_UPLOAD_CODE` to be configured.

### Storage Configuration

| Parameter       | Description                                                                      |
| --------------- | -------------------------------------------------------------------------------- |
| ALT\_FOLDER     | Additional local or mounted filesystem location where uploaded files are copied. |
| ENCRYPTION\_KEY | Base64-encoded encryption key used for supported external storage controllers.   |
| S3\_BUCKET      | Name of the S3-compatible storage bucket.                                        |
| S3\_ACCESS\_KEY | Access key used to connect to external storage.                                  |
| S3\_SECRET\_KEY | Secret key used to connect to external storage.                                  |
| S3\_ENDPOINT    | Endpoint URL of the S3-compatible storage service.                               |
| S3\_REGION      | Region associated with the storage bucket.                                       |

Additional FTP storage settings are available when using the corresponding storage controller.

The upstream documentation also lists some legacy or planned configuration options that are not implemented. Do not rely on `UPLOAD_QUOTA`, `MAX_RESIZED_IMAGES`, or the documented Redis worker settings as active functionality without verifying the selected version.

The exact configuration parameters depend on the Esadax deployment package. Use the parameters presented during the purchase and deployment process.

Once the required values are configured, click **Deploy** to launch PictShare.

## Docker Deployment

PictShare provides an official Docker image:

`ghcr.io/hascheksolutions/pictshare`

The standard deployment can be started with the following command:

```bash
docker run -d \
  -p 8080:80 \
  --name pictshare \
  ghcr.io/hascheksolutions/pictshare

```

The application listens on container port `80`.

The external port can be mapped according to your deployment environment.

For persistent deployments, configure a volume for uploaded files and preserve the application configuration.

PictShare also provides a Docker Compose configuration that can build the application locally and load settings from a `.env` file.

## Storage and Persistence

PictShare uses file-based storage instead of a conventional relational database.

Uploaded media is stored on the filesystem or through configured external storage controllers.

The standard Docker deployment uses `/data` as its persistent upload directory.

For reliable operation:

- Mount `/data` to persistent storage.
- Back up uploaded files regularly.
- Preserve the configuration file.
- Include external storage credentials in secure backups.
- Protect storage encryption keys separately.
- Monitor disk capacity and upload volume.
- Test recovery procedures.

Because uploaded files are stored independently of a database, basic backups can be performed by copying the relevant files and preserving their directory structure.

When using encrypted external storage, the encryption key must also be retained securely to ensure that uploaded content remains accessible.

## Scalability and Performance

PictShare can be scaled through external storage and multiple application instances.

S3-compatible storage and network-mounted directories allow multiple instances to access the same uploaded content.

Performance can be improved through:

- SSD-backed local storage
- Efficient PHP and web-server configuration
- Browser-compatible WebP delivery
- Duplicate detection
- External object storage
- Appropriate image compression settings
- Dedicated FFmpeg workers for video conversions
- Reverse proxy caching where appropriate

Image and video transformations consume server resources, particularly when processing large files or generating multiple versions.

For installations handling substantial video traffic, consider separating media-processing workloads from ordinary upload and download requests.

## Conclusion

PictShare is a lightweight, open-source file-sharing platform designed to simplify uploading, transforming, and distributing images, videos, audio, and text snippets.

With its URL-based image processing, upload API, duplicate detection, shareable albums, external storage integrations, and built-in MCP server, it provides more functionality than a conventional image-hosting application while maintaining a relatively simple deployment model.

Its database-free architecture, Docker support, and flexible storage options make it particularly suitable for homelabs, developers, and organizations that need a self-hosted alternative to public file-sharing services.

PictShare is a practical solution for building a centralized media upload endpoint that can be integrated into websites, applications, scripts, and automated workflows.

## Official Resources

- [PictShare GitHub Repository](https://github.com/HaschekSolutions/pictshare?ref=blog.esadax.com)
- [PictShare Official Website](https://pictshare.net/?ref=blog.esadax.com)
- [Configuration Reference](https://github.com/HaschekSolutions/pictshare/blob/master/rtfm/CONFIG.md?ref=blog.esadax.com)
- [API Documentation](https://github.com/HaschekSolutions/pictshare/blob/master/rtfm/API.md?ref=blog.esadax.com)
- [Docker Image](https://github.com/HaschekSolutions/pictshare/pkgs/container/pictshare?ref=blog.esadax.com)
- [MCP Documentation](https://github.com/HaschekSolutions/pictshare/blob/master/rtfm/MCP.md?ref=blog.esadax.com)