MergeImage · Last verified 2026-07-31

MergeImage Terms of Service

These Terms of Service govern use of mergeimage.app and its browser-based image-combining tool. By using the site, you agree to use it lawfully, respect rights in the files you select, and review the output before relying on it.

01

Using the service

The core tool is provided for lawful image combining

MergeImage provides a browser interface that can arrange compatible images horizontally, vertically, in a grid, or as a smart stitched screenshot and export PNG, JPEG, or WebP. The initial service is free and does not require an account. You are responsible for using a compatible browser and device.

You may use the tool for personal, educational, creative, or commercial workflows when you have the legal right to use the source material. You must not use the service to violate copyright, privacy, publicity, confidentiality, contract, or other rights, or to create or distribute unlawful material.

The service does not grant rights to images you select. Local processing does not make an unauthorized use lawful. Keep evidence of licenses or permissions when a destination, client, or platform requires it.

  • Use only files you are allowed to process.
  • Do not attempt to disrupt, probe, overload, or bypass the site.
  • Review the order, crop, dimensions, and content of every output.
  • Follow the rules of any platform where you upload the result.

02

Local processing and product limits

Your device performs the core composition

The core tool reads files you explicitly select and processes them in the current browser. MergeImage does not provide cloud backup for originals, working state, or downloads. You are responsible for retaining source files and saving a completed result before closing the page.

The initial workspace accepts up to 30 images, limits each selected file to 20 MB, and supports four layouts and three export formats. Outputs above a 12,000-pixel edge or 80 megapixels are proportionally reduced. These values may change as compatibility and safety are tested.

A browser may reject a file despite its extension, run out of memory below the published safety limit, or lack a requested encoder. Error messages and previews help, but they cannot cover every device, extension, or corrupted file. You should keep originals and test important outputs independently.

Responsibilities around a MergeImage session
AreaMergeImage providesYou are responsible for
Source filesLocal selection and decoding attemptRights, backups, and safe content
CompositionLayout controls and previewOrder, settings, and visual review
ExportBrowser-generated PNG, JPEG, or WebPDestination compatibility and retained copy
AvailabilityPublic web interface when operationalA suitable device, browser, and connection to load the site

03

Acceptable use and service integrity

Do not interfere with the site or other people

Do not use automated requests, malicious files, security probes, denial-of-service techniques, or other activity intended to damage, overload, or bypass the public site. Do not misrepresent an output as authentic evidence when edits, omissions, or arrangement change its meaning.

Do not use the service to exploit or harm children, disclose confidential information without authority, impersonate another person, facilitate fraud, or distribute malware. Applicable laws and platform rules may impose additional restrictions based on your location and use case.

We may restrict access to protect the site, comply with law, or respond to misuse. Because the initial tool has no account system, controls may apply to requests or public access rather than an individual account. These terms do not promise advance notice where immediate protection is reasonably necessary.

04

Intellectual property and feedback

Your files remain yours; the site implementation remains protected

As between you and MergeImage, you retain whatever rights you already hold in the source files and output. The tool does not claim ownership merely because the browser processes an image. You also remain responsible for third-party rights embedded in those files.

The site design, original copy, brand identifiers, and implementation may be protected by applicable intellectual-property laws. These terms allow ordinary use of the public tool, not copying the service, presenting it as your own, or removing notices from site materials.

If you send feedback, you permit the project to use the ideas to improve the service without an obligation to pay or implement them. Do not send confidential business information as feedback. A bug report should use non-sensitive fixtures whenever possible.

05

Availability, disclaimers, and liability

Preview and verify outputs before relying on them

The service is provided on an “as available” basis. Browsers, devices, hosting, and formats change, so uninterrupted access or perfect compatibility cannot be guaranteed. Features may be corrected, changed, or removed when necessary for safety, clarity, or maintenance.

To the extent permitted by applicable law, the service is provided without warranties of merchantability, fitness for a particular purpose, non-infringement, or error-free operation. Nothing here excludes a warranty or right that cannot legally be excluded in your jurisdiction.

To the extent permitted by law, MergeImage is not responsible for indirect, incidental, special, consequential, or lost-profit damages arising from use or inability to use the service. You remain responsible for backups, rights, settings, output review, and the consequences of publishing a composition.

06

Changes, governing principles, and contact

Current terms should match the current product

These terms describe the initial product verified on 2026-07-31. Material changes to accounts, paid features, remote processing, storage, or dispute procedures require an updated version. Continued use after a visible update may constitute acceptance where permitted.

Applicable mandatory consumer and local laws continue to apply. Because no operator jurisdiction or legal entity has been published, these terms do not invent a governing court, address, or registration. A complete jurisdiction clause should be added only when accurate operator information is available.

Questions about these terms can be sent to mergeimage@gmail.com. Do not attach confidential images. The W3C File API and MDN canvas documentation are linked to explain technical browser primitives, not to provide legal advice or endorse the service.

Last verified · 2026-07-31

Product facts

Primary and official references used on this page.

  • All decoding, arranging, and encoding runs locally in the current browser; the product sends 0 image files to a MergeImage server.
  • A workspace accepts up to 30 images and 20 MB per input file, with a 12,000 px or 80 MP output safety scale.
  • The verified build offers 4 layouts and 3 export formats: PNG, JPEG, and WebP, checked on 2026-07-31.
Product facts
Product facts Sources Last verified
30Product facts2026-07-31
20 MBProduct facts2026-07-31
12,000 px / 80 MPProduct facts2026-07-31
“The HTMLCanvasElement.toBlob() method creates a Blob object representing the image contained in the canvas.”

Sources

  1. Window: createImageBitmap() — MDN Web Docs
  2. HTMLCanvasElement: toBlob() — MDN Web Docs
  3. File API specification — W3C

Frequently asked questions

Do I keep rights in my images?

You keep whatever rights you already have. The tool does not grant rights to third-party material and does not claim ownership because a file was processed locally.

Can I rely on the output without checking it?

No. Preview and inspect order, seams, dimensions, text readability, and destination compatibility before using an output for an important purpose.

Can the service limits change?

Yes. Limits and formats may change for compatibility, safety, or maintenance, and material changes should be reflected in the visible site copy and terms.