---
title: "Web, Git & Developer Workflows"
url: "https://pixeltamp.com/help/web-and-developer-workflows"
description: "Keep Git repositories lean, save CI build minutes, and compress screen recordings for GitHub and Linear ticket limits."
---

# Web, Git & Developer Workflows

Building modern websites, web applications, and documentation requires balancing rich visual media with lean codebases and fast pipelines. PixelTamp fits directly into developer workflows on macOS, helping you keep repositories clean, reduce cloud build costs, and streamline issue reporting.

* * *

## 1\. Keeping Git Repositories Lean (Pre-Commit Diet)

Committing raw, multi-megabyte media assets directly into a Git repository creates permanent bloat:

-   **Git never forgets:** Even if you delete or replace an uncompressed 20MB hero image in a later commit, the heavy binary object remains permanently in the `.git` packfile history for every future developer who clones the project.
-   **Git LFS complexity:** While Git Large File Storage (LFS) manages binary assets outside repository packfiles, it introduces extra setup steps, bandwidth quotas, and third-party hosting dependencies.
-   **The pre-commit solution:** Run screenshots, brand marks, and photography through PixelTamp before staging them in Git. By converting heavy PNGs to modern WebP or applying the _Tamped_ preset, assets take up minimal disk space from their very first commit.

* * *

## 2\. Saving CI/CD Build Minutes & Preventing Timeouts

Many modern static site generators and web frameworks (such as Astro, Next.js, and Hugo) support on-the-fly image optimisation during build time using libraries like Sharp or Squoosh.

While convenient for small projects, processing hundreds of high-resolution images in CI/CD environments (such as GitHub Actions, GitLab CI, or Vercel) introduces real operational bottlenecks:

-   **Paid runner minutes:** Image decoders and encoders are CPU and memory intensive. Running full batch transformations during every pull request burns through monthly free tier build minutes quickly.
-   **Build timeouts and memory spikes:** Heavy image transformations can trigger out-of-memory errors on standard CI virtual machines with 7GB memory limits.
-   **The PixelTamp approach:** Optimise primary assets locally on your Mac before committing them. This allows your CI builds to run in seconds rather than minutes, treating static assets as pre-built artifacts.

* * *

## 3\. Screen Recordings for Issue Trackers & Pull Requests

When reporting bugs or demonstrating new UI features in issue trackers like **GitHub**, **Linear**, **Jira**, or **GitLab**, screen recordings are essential. However, default macOS QuickTime recordings cause friction:

-   **Bloated container sizes:** A 30-second macOS screen recording saved as a `.mov` file can easily exceed 80MB.
-   **Upload limits:** GitHub restricts file uploads to **10MB** or **25MB**, and Linear and Slack enforce similar attachment thresholds.
-   **Streaming delays:** Standard `.mov` containers store their index headers (the `moov` atom) at the very end of the file. Web browsers cannot begin playing the video until the entire file finishes downloading.

### How PixelTamp fixes screen recordings:

1.  Drop your `.mov` screen recording onto PixelTamp.
2.  Select the **Tamped** preset and ensure **MP4** is selected.
3.  PixelTamp leverages Apple Silicon hardware transcoding (VideoToolbox) to convert the video to a high-efficiency H.264 MP4, while automatically relocating the `moov` atom to the beginning of the file.

The resulting video is typically under 5MB, uploads instantly to GitHub pull requests or Linear issues, and streams inline immediately without buffering.

* * *

## 4\. Privacy & Client Non-Disclosure Agreements (NDAs)

Digital agencies, freelance developers, and internal engineering teams frequently handle unreleased product designs, client photography, and proprietary user interfaces.

Using browser-based compression websites often violates client NDAs:

-   Online compressors upload files to third-party cloud servers.
-   Files may be cached, scanned, or retained in remote logs without clear data retention guarantees.

PixelTamp operates **100% in-process on your Mac**. The application bundle requests zero network entitlements, meaning files never leave your workstation. You can safely compress confidential client media while remaining fully compliant with client contracts, GDPR, and enterprise security policies.