How Big Pixel Built Field Reporting That Preserves What Engineers Actually Capture

About Big Pixel

Big Pixel is a US-based custom software design and development company serving clients from startups to large enterprises. With a strong focus on UX and design, they operate as a fixed-fee shop, a model that distinguishes them from most competitors and holds them accountable to clearly defined project scope and outcomes.

Their work spans industries and application types, always with an emphasis on how design flows into the software and how the software serves the people using it.

The Challenge: Annotations That Disappeared at Export

Big Pixel was building a mobile application for an engineering firm whose teams work in the field every day, inspecting sites, running tests, and documenting findings through photographs taken directly on their phones.

The workflow was clear: engineers capture photos on-site, annotate them by drawing, circling, or highlighting areas of interest to emphasize findings, complete forms within the app, and then generate a structured field report for the client as a PDF.

The problem emerged at the final step. Every time the application generated a PDF, the annotation layer vanished. The photo came through. The drawing on top of it did not.

For an engineering firm where on-site markup is how findings are communicated to clients, this wasn't a minor visual issue, it was a fundamental gap in the product's value. Engineers were circling something specific for a reason. That context needed to survive into the final report.

Building a custom solution to handle image layering at that level would have been a significant engineering investment. Bending an existing reporting tool to accommodate it would have meant compromising on output quality. Neither option was acceptable.

“That little drawing layer every time we turn that into a PDF would go away.”
— David Baxter (Chief Pixel/ Strategist)

Why Image Layering Was the Make-or-Break Feature

Field reports are not just documents, they are evidence. When an engineer circles a crack in a foundation or highlights a faulty component, that markup carries meaning that plain text cannot replicate. The report's value depends entirely on the visual fidelity of what was captured and annotated in the field.

The challenge for Big Pixel was that standard PDF generation approaches treated images as flat assets. The annotation layer, built on top of the photo within the mobile app, existed as a separate element that wasn't being composited correctly into the final PDF output.

The team needed a library that could handle layered image composition cleanly and embed the result into a structured multi-page PDF without requiring them to build that capability themselves.

"You bring in other features that either you're going to have to custom build, which is a huge pain in the butt, or you're going to have to make the reporting tool kind of bend out of where they're comfortable." — Big Pixel

Solution

After evaluating their options, Big Pixel integrated IronPDF into their field reporting pipeline. The result was clean, reliable image layering that preserved everything engineers created on-site: annotations, drawings, and all directly within the generated PDF report.

Their implementation covers the core field reporting workflow:

Layered image composition for annotated field photos: engineers capture photos and draw annotations directly within the mobile app. IronPDF handles the composition of the base photo and the annotation layer into a single clean image within the PDF, preserving exactly what was marked up in the field. Explore IronPDF image handling

Multi-page field report generation: forms, images, and annotated photos are combined across pages into a single structured PDF report, ready to deliver to the client without manual post-processing. HTML to PDF tutorial

Mobile-to-PDF pipeline: the application allows engineering teams to generate complete reports from the field, with IronPDF handling the PDF output reliably across the full range of document content the app produces. Tutorial

IronPDF is part of Iron Suite, the complete collection of 10 .NET libraries from Iron Software covering PDF, Excel, OCR, barcodes, and more.

Real Results in Production

Field engineers can now annotate photos on their phones and trust that every circle, highlight, and markup will appear exactly as drawn in the final PDF delivered to the client. The field report arrives looking exactly as intended, with all visual evidence intact and in context.

For Big Pixel, IronPDF removed a layer of technical friction that would otherwise have required significant custom development or product compromise. The library handled a genuinely difficult compositing problem cleanly and fit into their existing workflow without requiring architectural changes.

The practical wins were significant:

Annotation preservation - drawing layers applied on-site within the mobile app survive the PDF export fully intact, maintaining the visual context engineers depend on.

Clean image layering - base photos and annotation layers are composited correctly into the PDF output without visual artifacts or missing elements.

Reduced custom development - a capability that would have required significant bespoke engineering was handled by the library, keeping the project on scope and on budget.

Reliable multi-page output - forms, photos, and annotated images combine consistently into structured, client-ready PDF reports across all report types the application generates.

Factors Driving Decisions

IronPDF is now the PDF generation layer for Big Pixel's field reporting application, handling the compositing and export requirements that other approaches couldn't reliably deliver.

Image compositing capability - IronPDF handled layered image composition cleanly, preserving annotation layers that were being lost with other approaches.

Developer integration - the library fit into the existing .NET application without requiring significant architectural changes or custom PDF handling infrastructure.

Output reliability - field reports generate consistently across the full range of content the application produces, from simple form data to complex annotated photo sequences.

Reduced engineering overhead - features that would have required custom development were available out of the box, keeping the project scope manageable.

Try IronPDF for FREE