Home Long-Term Rentals · Platform Audit

Does Property Meld support video inspections? Two answers, and they are different

Video files: yes, and generously, up to 100 MB each on any Meld. Inspections: not a native module, by design. Property Meld is the maintenance operations layer, and it routes inspections through partners rather than building its own. Here is every documented media path, role limit and API route we could verify against Property Meld's own pages.

By Sam ParksUpdated August 10, 20267 min read

Question 1: video files

Yes

Video attaches to any Meld, up to 100 MB per file, with a dedicated Videos filter in the file viewer. Managers, coordinators, technicians and vendors can upload any file type.

Question 2: inspections

Not native

There is no inspection module inside Property Meld. Inspections come from partners, and inspection findings arrive as automatically created Melds.

Property Meld supports video files but not video inspections. Its help documentation lists video formats such as mpeg, wmv and mov among the file types that attach to a Meld, capped at 100 MB per file, with a Videos filter in the file viewer. What it does not have is an inspection product. Property Meld's own integration-partners page keeps a separate Inspection Integrations category, where zInspector is the named partner and a second slot is marked Coming soon. Inspection findings become work orders in Property Meld; the inspection itself happens somewhere else.

What Property Meld is built to be

Reading a platform's media capability without reading its job description produces bad conclusions. Property Meld's homepage headline is "Transform maintenance into your #1 competitive advantage," and according to Property Meld's published product pages (propertymeld.com) the software is organized around five pillars: Communication, Scheduling, Oversight and Data, MAX Intelligence, and TrueCost. The markets it sells into are single-family, multifamily, HOA and student housing. Nowhere in that structure is there an inspections pillar, and that is a deliberate shape rather than an omission.

The shape is clearest in Nexus, Property Meld's partner ecosystem. According to Property Meld's Nexus page (propertymeld.com), Nexus "connects property managers, vendors, and service providers in one platform" and spans "inspections and sourcing to procurement and consulting." Inspections are named as an ecosystem function, sitting next to vendor sourcing, not as a feature of the core product. That is the single most useful thing to understand before you evaluate media in Property Meld: Property Meld is the place condition findings go, not the place they are captured.

The Vendor Nexus side of the same ecosystem reinforces it. Property Meld's vendor partner directory (propertymeld.com) carries listing pages for Inspectify, Seek Now, iVueit and PlanOmatic, four companies whose entire business is sending someone to a property to capture its condition. Property Meld's answer to "who documents the property" is a marketplace of people who do it, plus a software integration for the tool that structures it.

The evidence trail on media

Every row below is a verbatim line from Property Meld's own published documentation, with the role and limit it establishes. According to Property Meld's published help documentation (help.propertymeld.com), file handling on a Meld works like this.

Why files existHelp center
Attaching files to a Meld is useful for associating images of the condition or work performed. Condition media is framed around a work order, not a periodic inspection of the unit.
Video is supportedHelp center
Video files (ex. mpeg, wmv, mov, etc.) will appear with a default "video" thumbnail image. The file viewer's own filter list runs All, Photos, PDFs, Videos, Zip Files, and Other. Video is a first-class file class, not an accident.
The ceilingHelp center
Upload file size limit is 100 MB (per file). Generous for this category. A separate article puts manager uploads to a Unit record at 20 MB per file, so unit-level media is held to a tighter budget than Meld-level media.
Who can send videoHelp center
Residents can only upload Image or Photo file types. Vendors, maintenance coordinators and maintenance technicians can upload any file type. The resident restriction applies to the general upload area, and the MAX intake flow is the documented exception.
Resident video, at intakeHelp center
Upload Photos or Videos (Optional) Step 10 of Property Meld's guided MAX request flow. The product page for MAX puts it the same way: MAX "asks residents simple questions and prompts them to attach photos or videos."
Media by textHelp center
You can now reply to text notifications with attached photos or files to have them automatically added to the Meld. Documented for vendors and for residents. This is the lowest-friction capture path in the product, and it needs no login.
Sharing is explicitHelp center
Notifications are only sent from the Share operation, not by simply uploading a file. By default an owner is shared nothing, and files from a manager or vendor are not automatically shared with the resident. Vendors do see resident-uploaded images by default.

Two things stand out from that trail. First, Property Meld's media ceiling is high by the standards of this vertical: 100 MB per file with named video formats is a real allowance, not a token one, and it comfortably fits a short walkthrough clip. Second, all of it is anchored to a Meld. There is no unit-level condition record, no move-in and move-out pair, no baseline to compare against. That is exactly what you would expect from a platform whose unit of work is a repair.

Who can capture what, and where it lands

RolePhotosVideoDocumented path and limit
Resident Yes At intake Photos through the Meld upload area or by replying to a text notification. Video through the guided MAX request flow, which offers an optional photos-or-videos step. The general upload area is limited to image or photo types.
Technician Yes Yes Any file type, 100 MB per file. The technician mobile app surfaces "Attachments, including photos and documents" on a Meld, alongside work logs, costs and a resident signature.
Vendor Yes Yes "You can upload any file type," each under 100 MB, from desktop or mobile, or by replying to a text notification. Before-and-after photos are the documented use case.
Manager Yes Yes Any file type on a Meld at 100 MB per file, or on a Unit record at 20 MB per file. Multi-file download arrives as a single .zip.
Owner View only View only "By default, an Owner is not shared any file uploaded to a Meld. Explicit file sharing is required."

The resident row is the one worth sitting with if you are thinking about resident-recorded documentation. Property Meld already asks residents for video, already knows how to receive it, and already routes it to the right record. What it does not do is ask for that video on a schedule, against a template, or against what the unit looked like at move-in. That difference between tenant-guided inspections and reactive intake capture is the entire distance between a maintenance platform and an inspection platform.

How inspections actually reach Property Meld

Property Meld's integration-partners page (propertymeld.com) splits into two tabs, Accounting Integrations and Inspection Integrations, under the line "From accounting systems to inspections solutions, we're unifying the gap in property maintenance operations." The Inspection Integrations tab holds one named partner, zInspector, and one further card labelled Coming soon. A named vacancy on a partner page is a clear signal of intent: this is a category Property Meld plans to fill with partners rather than with product.

The mechanics are documented cleanly. According to Property Meld's help documentation (help.propertymeld.com), "Melds in Property Meld are automatically generated based on your inspection results in zInspector," with two behaviours worth knowing before you turn it on:

  • Only inspection-derived tasks sync. "Creating a task manually in zInspector will not create a Meld in Property Meld." The bridge is inspection findings, not the partner's task list.
  • Resident notification defaults off. "Melds created through the zInspector integration will default to 'No' for notifying residents," and residents have to be added manually afterwards. Sensible for findings a resident never reported, and easy to miss.
  • Data flows both ways on a schedule. zInspector syncs property and unit data from Property Meld every few hours, and matches against an accounting integration where one exists so records are not duplicated.

The connection itself is a handshake rather than a self-serve toggle: from Nexus, open Partner Nexus, configure the zInspector card, click Connect with this partner, and the request is submitted for the partner to complete. That is a well-run partner rail, and it tells you what Property Meld expects an inspection vendor to deliver: structured findings that become work orders.

The pattern across the category

Property Meld lands where most of the platforms in this audit series land, and the consistency matters more than any single finding. Maintenance and ops platforms accept generous media because a repair needs evidence, and they stop short of inspections because an inspection needs a schedule, a template and a baseline to compare against. We mapped every platform we could verify in the property management software video inspection matrix, and the split holds almost everywhere.

The API surface, and what it lets you build

Property Meld publishes real developer documentation, which is more than most of this category does. According to Property Meld's developer documentation (docs.propertymeld.com), the API "will provide you, the property management application developer, with everything you need to integrate with the leading property management maintenance solution." Authentication is an OAuth2 client-credentials exchange, and most endpoints additionally require an X-Multitenant-Id header naming the management company context.

Media is a genuine first-class citizen in that API. Uploads run as a two-step signed flow rather than a raw multipart POST, which is how you would build it if you expected large files:

POST /meld/generate-upload-url/"Generates a signed S3 upload URL for a file." Only management agents may set a file type other than meld_file.
POST /meld/{id}/add-media/"Associates a file that has been uploaded to S3 to a meld." Accepts an array, so a whole capture batch lands in one call.
GET /meld/{id}/file/resident/Per-Meld file lists, split three ways by resident, vendor and manager. Each record returns filename, uploader, created timestamp and a file URL.
POST /meld/{id}/media/The older single-step upload, marked deprecated in favour of the signed-URL pair above.

Three details are load-bearing if you are planning anything on top of it. The documented file-type enum is meld_file, signature and receipt, which is the API confirming the same story the product tells: files exist to serve a work order. The file-list endpoints partition by uploader role, so a system reading condition media can tell resident-captured evidence from vendor-captured evidence without guessing. And published rate limits are 50 requests per second for reads and 30 for writes, with a 429 on the far side, which is ample headroom for portfolio-scale media sync.

What is absent is equally informative: there is no inspection resource, no template resource and no condition-report resource anywhere in Property Meld's published route index. That is not a gap so much as a boundary line, and it is drawn in the same place on the product side and the API side.

Where the media goes next

Condition media does not stay put. According to Property Meld's help documentation (help.propertymeld.com), a Meld's files push downstream into the accounting system of record, and the fidelity varies by platform. On the AppFolio integration, Property Meld's outbound mapping is Files to Attachments and Files, so the media itself lands in AppFolio against the work order. On the Rent Manager integration the mapping is thinner: Meld Files to History and Notes, carrying the date the file was uploaded rather than the file. Worth knowing before you assume a downstream audit trail contains the images.

One direction is explicitly closed: on the AppFolio inbound side, unit "Photos: Does not import." Property Meld does not inherit a unit's existing photo library from the PMS, which means there is no move-in baseline waiting inside Property Meld for anything to compare against. If you want baseline comparison, it has to come from the layer that owns the inspection.

Working with Property Meld's design, not around it

The right way to run condition documentation in a Property Meld stack is the way Property Meld itself points you: keep inspection capture in a tool built for it, and let findings arrive in Property Meld as Melds. That is precisely the zInspector pattern, and it is the pattern every Nexus partner listing follows. Property Meld then does what it is genuinely excellent at, which is scheduling, dispatch, vendor coordination, resident communication and cost oversight on the work that results.

RapidEye slots into that same shape. A resident or a staff member records a walkthrough on a phone, RapidEye reviews it against that unit's own move-in baseline, and reports what actually changed, damage separated from ordinary wear. The output is a short list of findings with the evidence attached, which is the exact input a Meld wants. Your team opens a result rather than a submission, and the maintenance platform you already run keeps doing the coordination. For the reasoning behind recording the room rather than shooting a checklist, see video versus photo rental inspections; for what changes when the review is automated, see AI damage detection for long-term rentals.

Two practical notes for anyone building this stack today. Turn resident notification on deliberately for inspection-derived Melds, since the documented default is off. And decide early whether owners should see condition media, because Property Meld shares nothing with an owner unless you share it explicitly, which is a privacy-first default worth keeping and worth planning for.

Frequently asked questions

Can you upload a video to Property Meld?

Yes. Property Meld's help documentation lists video files such as mpeg, wmv and mov among the file types that attach to a Meld, and the file viewer includes a Videos filter. The documented ceiling is 100 MB per file for a Meld, and 20 MB per file when a manager uploads to a Unit record. Managers, maintenance coordinators, technicians and vendors can upload any file type; residents are limited to image or photo types in the general upload area.

Does Property Meld have a built-in inspection module?

No. Property Meld is a maintenance operations platform, and its published integration-partners page carries a dedicated Inspection Integrations category rather than a native inspections product. zInspector is the named inspection partner, connected through Partner Nexus, with a second inspection slot on the same page marked Coming soon.

Can residents record video for Property Meld?

Yes, at intake. Property Meld's MAX virtual maintenance assistant walks a resident through a guided request and offers an optional step to upload photos or videos. Outside that flow, the general file-upload area limits residents to image or photo file types, and residents can also reply to text notifications with photos or files to attach them to a Meld.

Can you pull Property Meld photos and videos out through the API?

Yes. Property Meld publishes an OAuth2 API with per-Meld file endpoints split by manager, resident and vendor, each returning a filename, uploader and file URL. Uploads run as a two-step flow: request a signed S3 upload URL, then associate the uploaded key to the Meld. The documented file types are meld_file, signature and receipt, and no inspection resource appears in the published route index.

How do Property Meld customers add video inspections?

Through the layer Property Meld was designed to sit above. Inspections happen in a dedicated tool or through a resident-recorded walkthrough, findings become Melds, and Property Meld does what it is best at: scheduling, dispatch, vendor coordination and cost oversight. RapidEye works this way, reviewing a resident or staff walkthrough against the unit's own move-in baseline and reporting what changed.

Sources

Sources are named at the publisher level with their root domain, rather than linked or titled; every figure is verifiable at the named source. All Property Meld documentation was fetched and verified first-hand on August 10, 2026.

  1. Property Meld product, Nexus, integration-partner and vendor-partner pages, Property Meld, 2026 propertymeld.com
  2. Property Meld published help documentation on file handling, resident and vendor uploads, the MAX intake flow, the technician mobile app, the zInspector integration, and PMS information flow, Property Meld, 2025 to 2026 help.propertymeld.com
  3. Property Meld developer documentation, published API route index and OpenAPI definitions, Property Meld, 2026 docs.propertymeld.com

Keep reading